From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] KVM: X86: remove read buffer for mmio read
Date: Mon, 9 Jul 2012 16:26:02 +0300 [thread overview]
Message-ID: <20120709132602.GA7298@redhat.com> (raw)
In-Reply-To: <4FFAD341.3080508@redhat.com>
On Mon, Jul 09, 2012 at 03:49:05PM +0300, Avi Kivity wrote:
> On 07/09/2012 02:23 PM, Gleb Natapov wrote:
> >
> >> kvm-unit-tests.git has a test for xchg to mmio. Does it still work?
> >>
> >> I agree this code has to go, but it needs to be replaced by something.
> >> Maybe a .valid flag in struct operand.
> >>
> > Valid will not enough for that.
>
> If we make everything go through operands, any reason why not?
>
Ah I missed operand part. Thought about adding valid to x86.c mmio read
buffer. What about doing more complex things from MMIO, like task switch?
--
Gleb.
prev parent reply other threads:[~2012-07-09 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 9:02 [PATCH 1/2] KVM: X86: remove read buffer for mmio read Xiao Guangrong
2012-07-09 9:03 ` [PATCH 2/2] KVM: X86: introduce set_mmio_exit_info Xiao Guangrong
2012-07-09 11:15 ` [PATCH 1/2] KVM: X86: remove read buffer for mmio read Avi Kivity
2012-07-09 11:23 ` Gleb Natapov
2012-07-09 12:48 ` Avi Kivity
2012-07-09 12:49 ` Avi Kivity
2012-07-09 13:23 ` Xiao Guangrong
2012-07-09 13:26 ` Gleb Natapov
2012-07-09 13:34 ` Avi Kivity
2012-07-10 10:36 ` Gleb Natapov
2012-07-10 10:45 ` Avi Kivity
2012-07-10 10:48 ` Gleb Natapov
2012-07-10 12:50 ` Avi Kivity
2012-07-10 13:01 ` Gleb Natapov
2012-07-10 16:04 ` Avi Kivity
2012-07-09 13:26 ` Gleb Natapov [this message]
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=20120709132602.GA7298@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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.