From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Kevin Wolf <kwolf@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [RFC PATCH] emulator: Fix task switch into/out of VM86
Date: Tue, 10 Jan 2012 12:08:15 +0900 [thread overview]
Message-ID: <4F0BAB9F.9070806@oss.ntt.co.jp> (raw)
In-Reply-To: <1326139810-5448-1-git-send-email-kwolf@redhat.com>
(2012/01/10 5:10), Kevin Wolf wrote:
> * May the emulator access the vcpu or should this go through a new
> x86_emulate_ops.set_rflags function pointer?
I think the latter is better.
Accessing the vcpu from the emulator looks like a layer violation.
Takuya
next prev parent reply other threads:[~2012-01-10 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 20:10 [RFC PATCH] emulator: Fix task switch into/out of VM86 Kevin Wolf
2012-01-10 3:08 ` Takuya Yoshikawa [this message]
2012-01-10 4:07 ` Takuya Yoshikawa
2012-01-10 9:01 ` Gleb Natapov
2012-01-10 9:28 ` Kevin Wolf
2012-01-10 10:17 ` Gleb Natapov
2012-01-10 11:25 ` Kevin Wolf
2012-01-10 11:30 ` Gleb Natapov
2012-01-10 17:51 ` Joerg Roedel
2012-01-16 15:37 ` Kevin Wolf
2012-01-16 15:57 ` Joerg Roedel
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=4F0BAB9F.9070806@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox