search for: vt

...of a vector are anded/ored together. My approach thus far has been to extract the sub elements of the vector and and/or those elements. This is ok for 4 vectors of i32s, but becomes cumbersome for v16i8s. Example instruction: andx $dst $v1 Pattern: [(set RC:$dst, (and (i32 (vector_extract(vt VC:$src), 0 ) ), (and (i32 (vector_extract(vt VC:$src), 1 ) ), (and (i32 (vector_extract(vt VC:$src), 2 ) ), (i32 (vector_extract(vt VC:$src), 3 ) ) ) ) ) )] Is there a better way to do this? Regards --- Conor Mac Aoidh

To elaborate, it is not only cumbersome writing these patterns for vectors of 16 characters (v16i8), it does not work. When I compile with this pattern for an andx operation on v16i8: /[(set RC:$dst,// // (and (i8 (vector_extract(vt VC:$src), 0 ) ), // // (and (i8 (vector_extract(vt VC:$src), 1 ) ),// // (and (i8 (vector_extract(vt VC:$src), 2 ) ),// ////(and (i8 (vector_extract(vt VC:$src), 3 ) ),// // (and (i8 (vector_extract(vt VC:$src), 4 ) ),// // (and (i8 (vector_extract(vt VC:$src),...

Hi, I''m not able to activate VT-d on my PC due to a buggy BIOS. Xen fails to parse ACPI DMAR table. There is a problem with RMRR address range. My configuration is : - Debian Weezy - Xen version 4.1.2 (Debian 4.1.2-2) - Sabertooth X58 with last bios (1304) - i7 - 960 I have the following message : (XEN) [VT-D]dmar.c:704: Hos...

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-de...

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-de...

...seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to get this working. And, yes, VT and VT-d are enabled in my BIOS. 1) CentOS 5.2 SRPMS compiled with Xen 3.2.1. Adding pci=nommconf does not get it to boot. 2) Mercurial Xen-3.2-testing. Here, after adding pci=nommconf, I get: (XEN) [VT-D]dmar.c:441: RMRR is incorrect. (XEN) Failed to parse ACPI DMAR. Disabling VT-d. (XEN) [VT-...

We have an Intel VT system, and we have successfully installed Xen 3.0 on it, but we cannot find out how to run Windows as a guest OS. Someone on this mailing list has successfully done it, but did not say how. Thanks, - Hao _______________________________________________ Xen-users mailing list Xen-users@lists.x...

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU...

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU...

I installed the most current version of Wine and then installed Legacy 7.0 onto my Ubuntu 8.04. the installation seemed to 'take'. Unfortunately when I activate Legacy, all I get is a view 1/4 of the screen - not a full screen, just the upper left had corner which shows a partial Legacy screen. I did not get any 'runtime' errors - just the partial screen and the program will not

Hello all, please tell me, how can I be sure that my Xen installation is built with Intel VT-d support? Something like xm info | grep -i KEY-REGULAR-EXPRESSION xm dmesg | grep -i KEY-REGULAR-EXPRESSION What a line should I look for? And if my installation was really built with VT-d support, how can I be sure, that Xen has successfully initialized VT-d hardware? I have read [1] and...

Hi list, i have seen a lot of questions about VT-d on recent intel mobos. however, it seems that all tests are done on the newer socket 775-based xeon''s or core2''s, and not the 5000 series (socket 771 based). i was planning on getting a intel S5000V chipset, but found out that it does not support VT-d. Can anyone confirm a mobo...

...nfidence with R for statistical analysis, but not for simulation therefore I apologize for my ignorance. What I came up with is the following: ##general settings c<-0.5 lambda<-0.3 a<-c/lambda n<-500 ## Eq.12 (the v_t random walk) V_init_cond<-0 Et<-ts(rnorm(n+100,mean=0,sd=1)) Vt<-Et*0 Vt[1]<-V_init_cond+Et[1] for(i in 2:(n+100)) { Vt[i]<-Vt[i-1]+Et[i] } Vt<-ts(Vt[(length(Vt)-n+1):length(Vt)]) plot(Vt) ## Eq.13 (the strategy) Xt_init_cond<-0 Xt<-Xt_init_cond*0 Xt[2]<-c(Vt[1]-Pt[1]) for(i in 2:(n)){ Xt[i]<-c(Vt[i-1]-Pt[i-1]) } Xt<-ts(Xt[(length(Xt...

I found a bug in the expansion code for SUB going back to at least LLVM 2.6 and still shows up in trunk. case ISD::SUB: { EVT VT = Node->getValueType(0); assert(TLI.isOperationLegalOrCustom(ISD::ADD, VT) && TLI.isOperationLegalOrCustom(ISD::XOR, VT) && "Don't know how to expand this subtraction!"); Tmp1 = DAG.getNode(ISD::XOR, dl, VT, Node->getOperand(1),...

hi, This is what I get on the Intel DQ35JO. Is it critical? (XEN) Brought up 2 CPUs (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping har...

Hello all, please tell me, how can I be sure that my Xen installation is built with Intel VT-d support? Something like xm info | grep -i KEY-REGULAR-EXPRESSION xm dmesg | grep -i KEY-REGULAR-EXPRESSION What line I should look for? And if it''s really built with it, how can I be sure, that Xen has successfully initialized VT-d hardware? I have read [1] and the lists archive...

...and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios and now all went fine. I saw this first with SLES11 SP1 but could reproduce it with the xen-unstable hypervisor. When I start the linux kernel native on the machine with or without VTd all is running very well. Following data: cpu: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz with inte...

I'm trying to understand why this assertion is here. LegalizeAction getCondCodeAction(ISD::CondCode CC, EVT VT) const { assert((unsigned)CC < array_lengthof(CondCodeActions) && (unsigned)VT.getSimpleVT().SimpleTy < sizeof(CondCodeActions[0])*4 && "Table isn't big enough!"); LegalizeAction Action = (LegalizeAction) ((CondCodeActions[C...

I have a chipset which supports VT-d (Intel X58) and, according to my motherboard manufacturers, VT-d is enabled in the BIOS and listed as "Intel VT." The problem is that xm dmesg shows "I/O virtualisation disabled" and I get this error message when I try to create a domU with a pci device assigned: ''Err...

...ion code. uint64_t > CondCodeActions[ISD::SETCC_INVALID]; > > What I suggest is the following: > Change the definition of CondCodeAction to: > uint64_t CondCodeActions[ISD::SETCC_INVALID][2]; > > setCondCodeAction then becomes: > void setCondCodeAction(ISD::CondCode CC, MVT VT, > LegalizeAction Action) { > assert(VT < MVT::LAST_VALUETYPE && > (unsigned)CC < array_lengthof(CondCodeActions) && > "Table isn't big enough!"); > CondCodeActions[(unsigned)CC][VT.SimplyTy...