search for: dexuan

The patch moves the struct IO_APIC_route_entry to a common place. This allows us to share the struct with iosapic. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I tried latest xen and linux-xen staging tree, but failed to run HVM domain on x86-64 environment. domU creation is OK. However the weird thing is not HVM domain itself. Instead system crashed on dom0 context. I saw once with some stack dump that xen''s page fault handler is executed on a dom0''s stack which then causes nested page fault due to unable to fetch vcpu pointer.

I think we need this feature at least for debugging purpose, right? Or, do we already have this feature? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...sheet, the PCI Express Capability Structure of the VF of Intel 82599 10GbE Controller looks trivial, e.g., the PCI Express Capabilities Register is 0, so the Capability Version is 0 and pt_pcie_size_init() would fail. We should not try to expose the PCIe cap of the device to guest. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> diff --git a/hw/pass-through.c b/hw/pass-through.c index f3d033b..360f2a1 100644 --- a/hw/pass-through.c +++ b/hw/pass-through.c @@ -2408,6 +2408,25 @@ out: return err; } +/* A return value of 1 means the capability should NOT be exposed to guest. */ +stati...

Any advice about the patch cr8-acceleration-3.patch? Hi Keir, could you give some comments? Thanks! -- Dexuan -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Cui, Dexuan Sent: 2006年10月25日 11:12 To: Keir.Fraser@cl.cam.ac.uk Cc: xen-devel@lists.xensource.com Subject: [Xen-devel] [Patch][RESEND] Add hardware CR8 acceleration f...

In x64 SMP Vista HVM guest (vcpus=2 in the configuration file), the wall clock time is 50% slower than that in the real world. The attached patch fixes the issue. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Changeset 15046:e527b4ff1948 breaks 32-bit HVM guest: when req->size is 4, "1UL << 32" returns 1 in IA32 system, so the mask becomes 0 wrongly. The attached patch fixes this by using 64-bit left-shift. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The PCI_EXP_TYPE_PCI_BRIDGE should be PCI_EXP_FLAGS_TYPE here. Also a tiny fix to the python comment. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...'s the purpose of re-initializing the hypercall page here? To improve the compatibility in the case the src/target hosts have different hypercall stub codes? PS, I''m using c/s 18353 to debug the issue. (the latest xen-unstable.hg''s S/R and L/M are broken by 18383. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...Bryan The BIOS version I use may be not the exact one as yours. I mean I expect you''re not using a very old BIOS. :-) How about trying the xen 3.2.2-rc2 and the latest xen-unstable first? There are some *VT-d* bug fixes between 3.2.1 (you''re using it) and 3.2.2-rc2. Thanks, -- Dexuan ________________________________ From: Kumar, Venkat [mailto:Venkat.Kumar@lsi.com] Sent: 2008年8月5日 14:37 To: Cui, Dexuan; xen-devel@lists.xensource.com Subject: RE: [Xen-devel] Xen-3.2.1 *VT-d* Support (NOT SURE WHETHER IT''S A BUG OR...) If you don''t mind can you send me the BI...

...he attached patch allows NMI to be injected to guest OS in NMIP capable platforms. It also enables to queue an NMI and then inject it as soon as possible. Signed-off-by: Haitao Shan <haitao.shan@intel.com> Signed-off-by: Eddie Dong <eddie.dong@intel.com> Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Please refer to the latest Intel SDM 3B (published in May, 2007): http://www.intel.com/products/processor/manuals/index.htm Best Regards Haitao Shan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http:/...

The Xen platform device (introduced in changeset 11161) would cause HCT''s PCI Compliance Test to generate a failure message. The patch fixes this. Thanks Dexuan Cui Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This adds a boolean boot parameter to xen to allow reserved memory regions to be added to the iommu mappings for dom0. The parameter is "iommu_include_reserved" and is off by default. A warning is also traced when incorrect RMRR to system memory map values are detected. This is being added to address some incorrect BIOS''s that do not report correctly the requied reserved memory

...sts.xensource.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Xen-devel digest..." Today's Topics: 1. Qemu nic rate limit (=?gb2312?B?yfLG9MH6?=) 2. [PATCH] xend: pci: find_parent: should return string rather than int (Cui, Dexuan) 3. Re: [PATCH] xend: pci: find_parent: should return string rather than int (Simon Horman) 4. RE: [PATCH] xend: pci: find_parent: should return string rather than int (Cui, Dexuan) ---------------------------------------------------------------------- Message: 1 Date: Wed, 17...

...a command "xm pci-list-assignable-devices" which can list all the assignable devices in the system. It is useful for end users. I made some tests on my hosts. Looks the patches work well. I''d like to ask for your comments, and test feedbacks. Thank you very much! Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...e memory block MUST be 1M-byte boundary aligned; if there are several such 1M memory blocks, HVM balloon driver should call invalidate_qemu_mapcache() several times, 1 block each time. The execution of invalidate_qemu_mapcache() is not slow -- 1000 times of invocation may take about 0.4 second. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ls/ http://download.intel.com/design/processor/specupdt/318148.pdf apicid_u8_2_u32.patch: changes the ''apicid'' from u8 to u32; x2apic.patch: replaces the traditional MMIO-style interface to the MSR-style one; uses physical fixed mode to deliver interrupts to CPU0. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I have successfully passed through a video card, network card, USB mouse, and USB keyboard to a MS Vista guest. That works well. I am trying to add another PCI device, such as a audio card or PCI USB hub, but I am running into a strange problem. When I plug the PCI audio (or USB card) to the motherboard. It makes it so that the PCI video card is no longer an "assignable device" (xm

...EN) HVM1: eip D3538 cs 10 eflags 2 (XEN) HVM1: uesp 0 uss 0 (XEN) HVM1: ves 0 vds 0 vfs 0 vgs 0 (XEN) HVM1: cr0 0 cr2 0 cr3 0 cr4 0 (XEN) HVM1: (XEN) HVM1: Halt called from %eip 0xD037C -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to