From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] memory: transaction API
Date: Thu, 21 Jul 2011 15:58:46 +0300 [thread overview]
Message-ID: <4E282286.2050508@redhat.com> (raw)
In-Reply-To: <4E28211C.5060705@siemens.com>
On 07/21/2011 03:52 PM, Jan Kiszka wrote:
> >
> > The problem is that "update" can change lots of things. offset, size,
> > whether it's mmio or RAM, read-onlyness, even the wierd things like
> > coalesced mmio. So it's either a function with 324.2 parameters (or a
> > large struct), or it's a series of functions with demarcation as to
> > where the update begins and ends.
>
> We do not need to provide update support for each and every bit, but for
> the common cases. memory_region_update_alias(region, offset, size) would
> be an excellent first candidate IMO.
It's not enough, look at cirrus and PAM.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-21 12:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 10:21 [PATCH] memory: transaction API Avi Kivity
2011-07-21 10:38 ` Jan Kiszka
2011-07-21 12:05 ` Avi Kivity
2011-07-21 12:08 ` Avi Kivity
2011-07-21 12:09 ` Jan Kiszka
2011-07-21 12:13 ` Avi Kivity
2011-07-21 12:52 ` Jan Kiszka
2011-07-21 12:58 ` Avi Kivity [this message]
2011-07-21 13:17 ` Jan Kiszka
2011-07-21 13:50 ` Avi Kivity
2011-07-21 14:32 ` Jan Kiszka
2011-07-21 14:39 ` Avi Kivity
2011-07-21 15:05 ` Jan Kiszka
2011-07-21 15:11 ` Avi Kivity
2011-07-21 11:04 ` Ferry Huberts
2011-07-21 12:07 ` Avi Kivity
2011-07-21 12:26 ` Ferry Huberts
2011-07-21 12:46 ` Avi Kivity
2011-07-21 12:56 ` Ferry Huberts
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=4E282286.2050508@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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