From: Scott Wood <scottwood@freescale.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH v2] qemu-kvm: Remove icache flush from cpu_physical_memory_rw
Date: Mon, 23 Jan 2012 18:26:06 -0600 [thread overview]
Message-ID: <4F1DFA9E.2010602@freescale.com> (raw)
In-Reply-To: <4F185B36.1070103@siemens.com>
On 01/19/2012 12:04 PM, Jan Kiszka wrote:
> On 2012-01-19 18:54, Marcelo Tosatti wrote:
>> On Thu, Jan 19, 2012 at 01:39:24PM +0100, Jan Kiszka wrote:
>>> This is at best a PPC topi but according to [1] even there unneeded. In
>>> any case, remove this diff to upstream, it should be handled there if
>>> actually needed.
>>
>> [1] ?
>>
>
> Oops.
>
> --------8<---------
>
> This is at best a PPC topi but according to [1] even there unneeded. In
> any case, remove this diff to upstream, it should be handled there if
> actually needed.
>
> [1] http://thread.gmane.org/gmane.comp.emulators.qemu/119022/focus=119086
That says that it's unneeded on (some?) IBM Power systems. We need it
on Freescale chips. I submitted an upstream-QEMU patch to do this flush
(referenced in that thread, still not applied) because I was seeing
cache problems when loading images.
-Scott
next prev parent reply other threads:[~2012-01-24 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:39 [PATCH] qemu-kvm: Remove icache flush from cpu_physical_memory_rw Jan Kiszka
2012-01-19 17:54 ` Marcelo Tosatti
2012-01-19 18:04 ` [PATCH v2] " Jan Kiszka
2012-01-20 10:25 ` Marcelo Tosatti
2012-01-24 0:26 ` Scott Wood [this message]
2012-01-24 8:57 ` Jan Kiszka
2012-01-24 11:34 ` Avi Kivity
2012-01-24 11:38 ` Jan Kiszka
2012-01-24 13:09 ` Avi Kivity
2012-01-24 13:12 ` Jan Kiszka
2012-01-24 13:26 ` Avi Kivity
2012-01-24 13:29 ` Jan Kiszka
2012-01-25 14:23 ` Alexander Graf
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=4F1DFA9E.2010602@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 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.