From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, paul.durrant@citrix.com,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] x86/emulate: implement hvmemul_cmpxchg() with an actual CMPXCHG
Date: Sun, 9 Apr 2017 14:03:24 +0300 [thread overview]
Message-ID: <0691b9a9-1555-4c22-6b92-7aabcc086122@bitdefender.com> (raw)
In-Reply-To: <3f469348-2cbd-834b-b802-66de23475706@bitdefender.com>
On 04/09/2017 01:15 AM, Razvan Cojocaru wrote:
> I'm not sure that it does not mess with the
> interrupt part of hvm_do_resume().
Actually I've now printk()ed
v->arch.hvm_vcpu.inject_event.vector on the EXCEPTION case of
hvm_emulate_one_vm_event(), and it's
always -1 in my tests, so the interrupt theory doesn't check out. I'll
have to think about another scenario to test.
Thanks,
Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-09 11:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 13:24 [PATCH RFC] x86/emulate: implement hvmemul_cmpxchg() with an actual CMPXCHG Razvan Cojocaru
2017-03-28 9:14 ` Razvan Cojocaru
2017-03-28 10:03 ` Jan Beulich
2017-03-28 10:25 ` Andrew Cooper
2017-03-28 10:44 ` Jan Beulich
2017-03-29 5:59 ` Jan Beulich
2017-03-29 8:14 ` Razvan Cojocaru
2017-03-28 10:27 ` Razvan Cojocaru
2017-03-28 10:47 ` Jan Beulich
2017-03-28 10:50 ` Razvan Cojocaru
2017-03-28 11:32 ` Jan Beulich
2017-03-29 13:55 ` Jan Beulich
2017-03-29 14:00 ` Razvan Cojocaru
2017-03-29 15:04 ` Razvan Cojocaru
2017-03-29 15:49 ` Razvan Cojocaru
2017-03-30 12:05 ` Jan Beulich
2017-03-30 12:25 ` Razvan Cojocaru
2017-03-30 12:56 ` Razvan Cojocaru
2017-03-30 14:08 ` Razvan Cojocaru
2017-03-30 14:21 ` Jan Beulich
2017-03-30 15:05 ` Razvan Cojocaru
2017-03-30 15:47 ` Jan Beulich
2017-03-31 6:17 ` Razvan Cojocaru
2017-03-31 7:34 ` Jan Beulich
2017-03-31 9:56 ` Razvan Cojocaru
2017-03-31 14:46 ` Jan Beulich
2017-03-31 15:01 ` Razvan Cojocaru
2017-03-31 15:04 ` Jan Beulich
2017-04-01 16:56 ` Razvan Cojocaru
2017-04-03 10:23 ` Jan Beulich
2017-04-03 18:20 ` Razvan Cojocaru
2017-04-03 18:36 ` Razvan Cojocaru
2017-04-04 9:07 ` Jan Beulich
2017-04-04 12:01 ` Razvan Cojocaru
2017-04-08 22:15 ` Razvan Cojocaru
2017-04-09 11:03 ` Razvan Cojocaru [this message]
2017-04-10 10:18 ` Jan Beulich
2017-03-29 14:12 ` Razvan Cojocaru
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=0691b9a9-1555-4c22-6b92-7aabcc086122@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.