similar to: HVM crash system on AMD APU A8-6600K

I have same problem described in earlier thread: http://lists.xen.org/archives/html/xen-devel/2013-08/msg01395.html Trying to start HVM domain leads to dom0 crash (simple cold reboot). My system is openSUSE 13.1 RC2 with Xen 4.3.0 My hardware is ASRock FM2A75 Pro4 AMD A8-6600K APU Gigabyte Radeon 7850 8 Gb DDR3 1600Mhz I have setup serial console and could provide logs your requested.

From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> This patch add an additional logic to check for the often case when the special->handle is not initialized due to firmware bugs. but the special->usedid is correct. If users overide this using the command line option ivrs_ioapic, then it should use the value instead. --- This patch is supposed to follow the patches:

Another bundle of issues from Coverity triage. The first one is in x86/mm, and looks scarier than it is. The others are all in xen/drivers and AFAICT are pretty minor. Cheers, Tim.

This applies to both SVM and VMX. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/hvm/svm/vmcb.c +++ b/xen/arch/x86/hvm/svm/vmcb.c @@ -310,7 +310,7 @@ static struct keyhandler vmcb_dump_keyha .desc = "dump AMD-V VMCBs" }; -void setup_vmcb_dump(void) +void __init setup_vmcb_dump(void) { register_keyhandler(''v'',

From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> This patch handle additional cases for IVRS bugs where special->handle is not correctly initialized for IOAPIC and HPETS due to firmware bugs. Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> Provide logic in "is_ioapic_overidden()" Signed-off-by: Jan Beulich <JBeulich@suse.com> ---

There are basically three issues we''re waiting to sort out (see below for more info): * XSA-55 * cpu hotplug in qemu-upsream * The MMIO hole issue Unfortuantely, there is considerable uncertainty about how long it will take for each of those to complete. We''re hoping to be able to release maybe on the 19th, This information will be mirrored on the Xen 4.3 Roadmap wiki page:

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Signed-off-by: Jan Beulich

From e2d47e2f75bac6876b7c2eaecfe946966bf27516 Mon Sep 17 00:00:00 2001 From: Liu Jinsong <jinsong.liu@intel.com> Date: Tue, 26 Nov 2013 04:53:17 +0800 Subject: [PATCH] VMX: wbinvd when vmentry under UC This patch flush cache when vmentry back to UC guest, to prevent cache polluted by hypervisor access guest memory during UC mode. However, wbinvd is a _very_ time consuming operation, so 1.

Hi Tim, Could you please have a look at this bug? Thanks a lot. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1774 Best Regards, Yongjie Ren (Jay) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Jan, Attached patch dumps io page fault flags. The flags show the reason of the fault and tell us if this is an unmapped interrupt fault or a DMA fault. Thanks, Wei signed-off-by: Wei Wang <wei.wang2@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have

flight 19723 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/19723/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 9 guest-start fail REGR. vs. 19708 test-amd64-i386-xend-winxpsp3 8 guest-saverestore fail REGR. vs. 19708 test-amd64-i386-pv 9

Hi! From other people posting to this list, I know that there has been a bug related to the issue described in Xen Security Advisory 36 that disables iommu for some AMD users like me. However, even when passing "iommu=no-amd-iommu-perdev-intremap" it still disables i/o virtualisatoin. Related Xen dmesg output: (XEN) IVHD Error: Invalid IO-APIC 0 (XEN) AMD-Vi: Error initialization

Guys Is it possible to passtrough iGPU from AMD A10-7870K to kvm virtual machine? If so then how please? Thank you David

Turns out we used a misaligned long instruction near the end, and the shader was getting killed after writing R, A components. This has gone unnoticed since the remaining G, B outputs aren't actually used. --- src/nv50_accel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/nv50_accel.c b/src/nv50_accel.c index 5fa539c..1218e18 100644 --- a/src/nv50_accel.c

嬥堜桪巕偲怽偟傑偡丅 撍慠偺儊乕儖憲怣丄怽偟栿偛偞偄傑偣傫丅 僗億儞僒乕僒僀僩條傛傝擇恖偺彈惈偺徯夘埶棅傪庴偗傑偟偨偺偱丄 偛埬撪偝偣偰偔偩偝偄丅丅 堦愗椏嬥柍偟偺偛徯夘偲側傝傑偡丅 儊乕儖偺憲庴怣傪娷傔丄偳傟偩偗棙梡偟偰捀偄偰傕柍椏偱偡丅 姰慡柍椏偱偺偛徯夘偱偡偺偱憗婜掲傔愗傝偺応崌偑偛偞偄傑偡丅 傑偨丄掲傔愗傝偲側偭偨偲偒偼梊崘側偔彈惈偺曄峏傪偡傞応崌傕偛偞偄傑偡偑丄 偛梕幫偔偩偝偄丅 僋儕僢僋佀丂http://chestnut.happydeeds.com/a12/

On 2013-10-18 7:11 AM, Sebastian Reimers wrote: > Hello!, > > i've just compared the 1.0.3 release with the master branch > on a BeagleBone Black (AM335x 1GHz ARM Cortex-A8 with NEON > floating-point accelerator) and Arch Linux ARM. > > At the moment I dont no why, but I see that 1.1 is much slower > in encoding. Are there any default changes, that I missed and could

I wrote: > In a floating point build > it's enabled only at complexity setting 10 Sorry. I meant that in a _fixed_point_ build the new analysis code is enabled only at complexity setting 10. It's currently enabled for floating point builds at complexity 7 or higher. Both fixed and float builds default to complexity 9 in 1.1. -r

On Fri, Oct 18, 2013 at 2:21 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Just to clear things up... So 1.1 has some new analysis code that > increases the amount of CPU. When building as floating point (which you > appear to be doing, right?), the new code is enabled at complexity 7 and > up (opusenc defaults to complexity 10 IIRC). This is why you've been >

hi all I saw that llvm-2.7 support arm cortex-a8 now, but I didn't find how to cross build it. thank you all -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100505/976c140e/attachment.html>