 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] x86/amd: fix crash as Xen Dom0 on AMD Trinity systems
 On 05/31/2012 12:33 AM, Konrad Rzeszutek Wilk wrote: Now, someone probably needs to paravirt the *safe_regs variants in case something else decides to use them. I don't know what to do here, do I want more paravirt code in there? No. I guess if this is done carefully and cleanly, then it should be ok but it can't be done like that - it needs to adhere to the current pv_cpu_ops thing which is already there.Using the native variant seems the right thing to do.I thought I was being told that Xen would trap and emulate the rdmsr/wrmsr instructions. I guess they don't want to do that for theIt does.handful of performance-sensitive MSRs there are, but those don't use the *_regs variants. Acked-by: Andre Przywara <andre.przywara@xxxxxxx> This works on the test machine.Though I'd still like to have my original patch applied, because it makes the thing a bit cleaner. And I made a patch to remove the {rd,wr}msr_regs hooks from paravirt_ops completely. Shall I send it out or do you want to make this part of larger patch series to clean up pvops? Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel 
 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |