All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Scott Wood <scottwood@freescale.com>,
	Marcelo Tosatti <mtosatti@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: Tue, 24 Jan 2012 13:34:50 +0200	[thread overview]
Message-ID: <4F1E975A.10600@redhat.com> (raw)
In-Reply-To: <4F1E7266.5000800@siemens.com>

On 01/24/2012 10:57 AM, Jan Kiszka wrote:
> > 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.
>
> Then you probably want to limit your patch's effect to that particular
> set of chips and repost it to qemu-devel. In any case, it's not a
> qemu-kvm topic as we are x86-only for quite a while.
>

IIRC introduced for ia64.  But isn't the correct action adding it to
qemu.git instead of removing it completely?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-01-24 11:34 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
2012-01-24  8:57       ` Jan Kiszka
2012-01-24 11:34         ` Avi Kivity [this message]
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=4F1E975A.10600@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=scottwood@freescale.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.