qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Benoît Canet" <benoit.canet@gmail.com>,
	"Andreas Färber" <afaerber@suse.de>,
	patches@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 2/2] hw/integratorcp: Simplify flash remap code
Date: Sun, 08 Jan 2012 13:16:57 +0200	[thread overview]
Message-ID: <4F097B29.7040608@redhat.com> (raw)
In-Reply-To: <CAFEAcA_zXh-sKdFSGQSec=1VyMWO6Y4t7WgwK=xisZPd3jiogw@mail.gmail.com>

On 01/07/2012 06:09 PM, Peter Maydell wrote:
> On 7 January 2012 04:40, Andreas Färber <afaerber@suse.de> wrote:
> > I noticed you're dropping a comment about tlb_flush(). Is that because
> > it was dead code, or does the Memory API take care of it for us?
> > (I assume the former because memory_region_set_enabled() does not take a
> > CPUState* to operate on.)
>
> Arranging for a tlb_flush if needed has to be the Memory API's
> problem, because everything that uses the memory API to rearrange
> the view of the address space has exactly the same requirement that
> anything else in QEMU has to be told it may need to redo any caching
> data structure it has set up. In particular, this doesn't apply just
> for a single CPUState* -- in a multicore system every CPU has to be
> made aware that the world has changed, not just the one which
> happened to do the store to the "remap the flash" register.
> Also the memory API is the only thing that knows whether the region
> was already enabled (ie this is a no-op), whether some other region
> is overlapping so in fact it makes no difference whether we enable
> or disable this one, etc etc).
>
> So basically I dropped that line because it was a bit of commented
> out code with a ??? marker appended, and the device layer is the
> wrong place to be trying to solve the issue it was gesturing at.
>

Correct, and the memory core will flush the tlb, so all is well.

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

  reply	other threads:[~2012-01-08 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 18:58 [Qemu-devel] [PATCH v4 0/2] integratorcp: fix and simplify flash remap code Peter Maydell
2012-01-06 18:58 ` [Qemu-devel] [PATCH v4 1/2] hw/integratorcp: Fix sense of REMAP bit Peter Maydell
2012-01-10 17:35   ` andrzej zaborowski
2012-01-06 18:58 ` [Qemu-devel] [PATCH v4 2/2] hw/integratorcp: Simplify flash remap code Peter Maydell
2012-01-07  4:40   ` Andreas Färber
2012-01-07 16:09     ` Peter Maydell
2012-01-08 11:16       ` Avi Kivity [this message]
2012-01-08 11:19         ` Andreas Färber
2012-01-08 11:22           ` 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=4F097B29.7040608@redhat.com \
    --to=avi@redhat.com \
    --cc=afaerber@suse.de \
    --cc=benoit.canet@gmail.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).