From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <glommer@gmail.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
"Yang, Sheng" <sheng.yang@intel.com>,
kvm@vger.kernel.org, Glauber Costa <gcosta@redhat.com>
Subject: Re: [PATCH] mask out clflush
Date: Thu, 10 Jul 2008 17:47:54 +0300 [thread overview]
Message-ID: <4876211A.5030307@qumranet.com> (raw)
In-Reply-To: <5d6222a80807100745t6795084dsd78695ea69413a24@mail.gmail.com>
Glauber Costa wrote:
> On Thu, Jul 10, 2008 at 11:20 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Avi Kivity wrote:
>>
>>> Anthony Liguori wrote:
>>>
>>>> It's equivalent to a read from a VT perspective so if the read would
>>>> trap, the clflush instruction will trap.
>>>>
>>>>
>>> Reads don't normally go through the emulator. Is the guest clflush()ing
>>> mmio addresses? Strange as these are not normally cached.
>>>
>> It seems so, Glauber mentioned that the address was an MMIO address.
>>
>
> yes. It is address 0xc8821000, apparently part of a pci controller
> initialization.
>
qemu pci starts at 0xe0000000 IIRC. So maybe the guest is flushing
random addresses just to be annoying.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-10 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 18:29 [PATCH] mask out clflush Glauber Costa
2008-07-08 19:34 ` Anthony Liguori
2008-07-08 20:01 ` Glauber Costa
2008-07-10 10:43 ` Yang, Sheng
2008-07-10 13:30 ` Anthony Liguori
2008-07-10 13:34 ` Avi Kivity
2008-07-10 13:37 ` Anthony Liguori
2008-07-10 14:10 ` Avi Kivity
2008-07-10 14:20 ` Anthony Liguori
2008-07-10 14:45 ` Glauber Costa
2008-07-10 14:47 ` Avi Kivity [this message]
2008-07-10 15:37 ` Anthony Liguori
2008-07-10 15:39 ` Avi Kivity
2008-07-10 20:18 ` Glauber Costa
2008-07-13 7:58 ` Avi Kivity
2008-07-10 14:16 ` Avi Kivity
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=4876211A.5030307@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.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