From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Xu Zhang <zhxwhu@gmail.com>
Cc: gm281@cam.ac.uk, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Nested events in 64bit mini-OS
Date: Thu, 25 Oct 2012 22:56:53 +0200 [thread overview]
Message-ID: <20121025205653.GW5925@type.chello.at> (raw)
In-Reply-To: <50871D90.50606@gmail.com>
Xu Zhang, le Tue 23 Oct 2012 17:43:28 -0500, a écrit :
> 64-bit mini-OS seems to adopt a mixed use of both (in HYPERVISOR_IRET).
> mini-OS doesn't have an userspace, so unless an NMI happened, it always
> perform interrupt/exception return with machine instruction iret, without
> checking against nested events. This is wrong to me. Am I missing something
> here?
I don't think you are missing anything. Cc-ing Grzegorz, who actually
wrote the code.
Samuel
next prev parent reply other threads:[~2012-10-25 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 22:43 Nested events in 64bit mini-OS Xu Zhang
2012-10-25 20:56 ` Samuel Thibault [this message]
2012-11-06 5:56 ` Xu Zhang
2012-11-10 13:52 ` Samuel Thibault
2012-11-11 15:36 ` Xu Zhang
2012-11-14 1:49 ` Xu Zhang
2012-11-18 17:43 ` Samuel Thibault
2012-11-19 10:22 ` Ian Campbell
2012-11-19 10:21 ` Ian Campbell
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=20121025205653.GW5925@type.chello.at \
--to=samuel.thibault@ens-lyon.org \
--cc=gm281@cam.ac.uk \
--cc=xen-devel@lists.xen.org \
--cc=zhxwhu@gmail.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.