All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Mark Langsdorf <mark.langsdorf@amd.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: SimNow not emulating xsave in hwemu_family15.bsd
Date: Thu, 1 Apr 2010 13:58:42 +0200	[thread overview]
Message-ID: <4BB48A72.9060600@amd.com> (raw)

Hi,

while trying to use the latest Xen unstable inside SimNow, I learned 
that despite the respective CPUID flag is set, SimNow does not emualate 
at least the xsetbv instruction (part of to the XSAVE feature).
SimNow will answer with exception #6 (#UD) and Xen will crash. The CPUID 
bit is set, though (as in the real BD). When turning this bit off (in 
debugger: rMc0011004=1298220B178BFBFF, is there an easier way?), Xen 
will avoid the xsetbv call and the guest creation process continues.

Can the SimNow tell us the recommended .bsd we should use for testing 
SVM features?

Thanks and
Regards,
Andre.

-- 
Andre Przywara
AMD-OSRC (Dresden)
Tel: x29712

             reply	other threads:[~2010-04-01 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 11:58 Andre Przywara [this message]
2010-04-01 12:06 ` SimNow not emulating xsave in hwemu_family15.bsd Andre Przywara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BB48A72.9060600@amd.com \
    --to=andre.przywara@amd.com \
    --cc=mark.langsdorf@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.