Displaying 8 results from an estimated 8 matches for "int0".
Did you mean:
int
2006 Sep 17
0
Weird DNAT + passive FTP bug
...l network card the flow looks
like this.
[ internal domain eth0 172.31.2.3 ]
|
... ... |
.----|---|----- vif3.0 ----.
| | | | |
|...-+---+----- xenbr0 |
| | |
| vif0.0 |
| 172.31.1.1 int0 |
| | |
| privil. domain NAT/route |
| | |
| 213.xxx.xxx.xxx | |
`--------------- eth0 -----''
For some reason (deadlocks), XEN doesn''t connect to xenbr0 directly but
via a loopback device (here vif0.0/int0), that...
2009 Feb 12
0
[LLVMdev] Eliminate PHI for non-copyable registers
On Feb 11, 2009, at 4:07 AM, Alex wrote:
> In my hardware there are two special registers cannot be copied but
> can only be assigned and referenced (read) in the other instruction.
> They are allocatable also.
>
> br i1 %if_cond, label %then, label %else
> then:
> %x1 = fptosi float %y1 to i32
> br label %endif
> else:
> %x2 = fptosi float %y2 to i32
>
2009 Feb 12
2
[LLVMdev] Eliminate PHI for non-copyable registers
...the hardware implements the same number
of these i32 registers as the "specification". The input language (which is
converted to LLVM IR) may use up to 4 registers but the hardware only has 2.
So they must be allocatable, right?
For example, the input uses up to 3 <i32> registers INT0, INT1, INT2 (Rx are
FP registers):
fp2int INT0, R0
fp2int INT1, R1
fp2int INT2, R2
add R0, R0, R[INT1+1]
mul R0, R[INT2+2], R[INT0+1]
Since the hardware doesn't has INT2, the final machine should be like:
fp2int INT0, R0
fp2int INT1, R1
add R0, R0, R[INT1+1]
fp2int INT1, R2...
2009 Feb 11
2
[LLVMdev] Eliminate PHI for non-copyable registers
In my hardware there are two special registers cannot be copied but can only
be assigned and referenced (read) in the other instruction. They are
allocatable also.
br i1 %if_cond, label %then, label %else
then:
%x1 = fptosi float %y1 to i32
br label %endif
else:
%x2 = fptosi float %y2 to i32
br label %endif
endif:
%x3 = phi i32 [%x1, %then], [%x2, %else]
PNE::LowerAtomiPHINode() fails
2005 Sep 22
2
Kernel building
I have not even decided if I want to undertake a kernel build, but for
the sake of discussion, if everything happens to be in the stock kernel,
why, other than file bloat, would you want to build a custom kernel? In
FreeBSD, you can remove all those devices and drivers that are not
needed, and, depending on how much stuff you add or delete, can make a
decent size reduction in the kernel
2019 May 10
5
Cannot get interface MTU - qemu quest fails to start off OpenVswitch
hi guys
I have a qemu guest and openvswitch bridge and the guest fails to start:
$ virsh start work8
error: Failed to start domain work8-vm-win2016
error: Cannot get interface MTU on 'ovsbr0': No such device
LXC guest which uses the same source network starts just fine.
I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from
centos-openstack-pike repo and
2007 Feb 22
3
Network problem: packets are lost in domU
Hello,
I am having big problems with Xen virtual network interfaces. First
I tried typical bridge support, no luck. The packets sent from dom0
to domU seemed to disappear somewhere. Then, to debug the problem
I have set up a simple point-to-point link and still have the same
problem.
I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU.
I have tried kernel 2.6.16.35 and 2.6.16.41.
I
2005 Oct 16
2
[LLVMdev] Help on LLVM Instrumentation
Hi ,
I am using LLVM for my Post Graduate course project on Optimization. I am trying to do some insrtumentation to the bytecode.I 've been going through your Instrumentation code for the past few days in /llvm/lib/Transforms/Instrumentation folder and finally found two ways of instrumentation :
1) injecting LLVM bytecode instructions
2) calling an external C function.
I am trying both and