From: Glauber Costa <glommer@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] remove smaller slots if registering a bigger one
Date: Wed, 11 Feb 2009 12:59:15 -0200 [thread overview]
Message-ID: <20090211145915.GB27729@poweredge.glommer> (raw)
In-Reply-To: <4992E499.8050502@siemens.com>
> >
> > Now, if you remember the last memory patches I sent, it actually removes
> > this line. However, this is because in that alternative, we were tracking
> > mmio regions in qemu, but not in kvm. so flags >= TLB_MMIO would just
> > delete it from the kernel mapping, but qemu would not forget about it.
> >
> > This is to show that I believe that it might be possible to handle mmio
> > regions slightly different, but I don't think just dropping this line would
> > help much.
>
> What confused me most here - and still does - is that TLB_* flags make
> semantically no sense to me in the physical memory
> registering/unregistering context. They should only show up in
> CPUTLBEntry, no? But maybe I'm overseeing some strange relation.
>
I might be wrong, but I believe it's used quite often in normal memory
to track pieces of memory in which we do mmio.
next prev parent reply other threads:[~2009-02-11 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 13:47 [Qemu-devel] [PATCH] remove smaller slots if registering a bigger one Glauber Costa
2009-02-11 14:23 ` [Qemu-devel] " Jan Kiszka
2009-02-11 14:36 ` Avi Kivity
2009-02-11 14:37 ` Glauber Costa
2009-02-11 14:45 ` Jan Kiszka
2009-02-11 14:52 ` Jan Kiszka
2009-02-11 14:59 ` Glauber Costa [this message]
2009-02-11 15:30 ` Avi Kivity
2009-02-11 16:47 ` Jan Kiszka
2009-02-11 16:56 ` 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=20090211145915.GB27729@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--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).