From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers
Date: Thu, 31 Mar 2011 22:03:00 +0200 [thread overview]
Message-ID: <20110331200300.GA26170@redhat.com> (raw)
In-Reply-To: <4D94D583.7050203@codemonkey.ws>
On Thu, Mar 31, 2011 at 02:26:59PM -0500, Anthony Liguori wrote:
> On 03/31/2011 02:07 PM, Michael S. Tsirkin wrote:
> >>Just needs some love.
> >>
> >>VGA is just another device. It happens to be that we treat VGA
> >>device memory as something that behaves like ram occassionally but
> >>that does not make it RAM.
> >If we agree on that, will a pair of functions for this work?
> >How about device_register_ram / device_unregister_ram ?
>
> To register normal RAM or to register stuff that isn't RAM but looks
> and tastes like RAM?
The later.
> >>Something like vhost doesn't need to see anything but RAM. If we
> >>have a mechanism to identify RAM as RAM, then vhost can only look at
> >>RAM memory and not worry about things like VGA.
> >>
> >>I thought Alex had gotten a mini-version of RamAPI in but I can't
> >>seem to figure out what that included.
> >Me neither.
> >
> >> At any rate, the point is
> >>still that registering things that you want to exclude in vhost is
> >>the wrong approach, you want to explicitly mark the things you want
> >>to include.
> >>
> >>Regards,
> >>
> >>Anthony Liguori
> >vhost just wants RAM.
>
> Right, so mark RAM, and call it a day :-)
>
> Regards,
>
> Anthony Liguori
>
next prev parent reply other threads:[~2011-03-31 20:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 17:43 [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers Michael S. Tsirkin
2011-03-31 18:33 ` Anthony Liguori
2011-03-31 18:49 ` Michael S. Tsirkin
2011-03-31 19:01 ` Anthony Liguori
2011-03-31 19:07 ` Michael S. Tsirkin
2011-03-31 19:26 ` Anthony Liguori
2011-03-31 20:03 ` Michael S. Tsirkin [this message]
2011-03-31 20:21 ` Anthony Liguori
2011-03-31 19:17 ` Alex Williamson
2011-03-31 19:18 ` Peter Maydell
2011-03-31 19:29 ` Anthony Liguori
2011-03-31 20:12 ` Peter Maydell
2011-03-31 20:23 ` Anthony Liguori
2011-03-31 21:32 ` Peter Maydell
2011-03-31 21:38 ` Michael S. Tsirkin
2011-03-31 21:49 ` Anthony Liguori
2011-03-31 23:42 ` Michael S. Tsirkin
2011-04-01 0:44 ` Anthony Liguori
2011-04-01 1:07 ` Michael S. Tsirkin
2011-04-01 7:12 ` Peter Maydell
2011-04-01 11:21 ` Michael S. Tsirkin
2011-03-31 21:26 ` Michael S. Tsirkin
2011-03-31 21:32 ` Anthony Liguori
2011-03-31 21:37 ` Michael S. Tsirkin
2011-03-31 21:48 ` Anthony Liguori
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=20110331200300.GA26170@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--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).