All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
	paul@codesourcery.com, qemu-devel@nongnu.org,
	Aurelien Jarno <aurelien@aurel32.net>,
	agraf@suse.de
Subject: [Qemu-devel] Re: [PATCHv2 0/3] rwhandler: introduce and switch pci_host to it
Date: Mon, 18 Jan 2010 19:53:25 +0200	[thread overview]
Message-ID: <20100118175325.GA15430@redhat.com> (raw)
In-Reply-To: <f43fc5581001180950n27e2fd48v38eab3c36a54f04f@mail.gmail.com>

On Mon, Jan 18, 2010 at 05:50:35PM +0000, Blue Swirl wrote:
> On Mon, Jan 18, 2010 at 10:56 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Alexander, so I assume the following patchset should be enough for you
> > to implement u3 support, simply by creating your own rwhandler, and
> > using pci_data_read/write directly there. I have pushed it to a
> > temporary branch in my tree:
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git rwhandler
> >
> > Paul, any comments on this approach?
> >
> > I'll push this to my pci tree if this turns out to be helpful.
> > Hope this helps, and sorry about the churn.
> 
> I proposed earlier something similar for MMIO. The thread could be interesting:
> http://lists.gnu.org/archive/html/qemu-devel/2009-05/msg00095.html

IIUC that patch seems to do much more, and also seems to involve all io?
This one is just a library that devices can use. Intended users are not
performance-critical like pci config.

-- 
MST

  reply	other threads:[~2010-01-18 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 10:56 [Qemu-devel] [PATCHv2 0/3] rwhandler: introduce and switch pci_host to it Michael S. Tsirkin
2010-01-18 17:50 ` [Qemu-devel] " Blue Swirl
2010-01-18 17:53   ` Michael S. Tsirkin [this message]
2010-01-18 19:41     ` Michael S. Tsirkin
2010-01-18 19:56       ` Blue Swirl

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=20100118175325.GA15430@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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.