From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Xu Zhang <xzhang@cs.uic.edu>
Cc: gm281@cam.ac.uk, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Nested events in 64bit mini-OS
Date: Sun, 18 Nov 2012 18:43:41 +0100 [thread overview]
Message-ID: <20121118174341.GB6017@type> (raw)
In-Reply-To: <50A2F8A7.5000202@cs.uic.edu>
Xu Zhang, le Tue 13 Nov 2012 19:49:27 -0600, a écrit :
> 1. if event is disabled: doesn't hurt to mask it again;
> 2. if event is enabled: we disable event, and jumps to hypercall_page to
> make a hypercall iret, which eventually calls do_iret:
>
> In do_iret, line 309:
> /* Restore upcall mask from supplied EFLAGS.IF. */
> vcpu_info(v, evtchn_upcall_mask) = !(iret_saved.rflags &
> X86_EFLAGS_IF);
Ah, right. Disabling events just before the jmp seems all right to me
then.
> Correct me if I am wrong, I think hypercall_page is mapped at runtime to
> guest OS by Xen. It's not actually part of the critical section of guest OS,
> at least not at compile time.
Sure. I meant it'd mean a second fixup table, but who knows what code is
there, it could be tampering with the stack.
> Following the discussion above, we could easily avoid such fixup table
> by mask out the events.
Completely.
Samuel
next prev parent reply other threads:[~2012-11-18 17:43 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
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 [this message]
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=20121118174341.GB6017@type \
--to=samuel.thibault@ens-lyon.org \
--cc=gm281@cam.ac.uk \
--cc=xen-devel@lists.xen.org \
--cc=xzhang@cs.uic.edu \
/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.