From: Gregory Haskins <gregory.haskins@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gregory Haskins <GHaskins@novell.com>,
mingo@elte.hu, alacrityvm-devel@lists.sourceforge.net,
mst@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model
Date: Tue, 18 Aug 2009 09:19:35 -0400 [thread overview]
Message-ID: <4A8AAA67.8060602@gmail.com> (raw)
In-Reply-To: <4A8AA0C6.805@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Avi Kivity wrote:
> On 08/18/2009 03:36 PM, Gregory Haskins wrote:
>> Yeah, I agree. I am not advocating we expend energy on this now. But
>> my thoughts at the time were that that particular problem can be
>> solved at io-setup time with some kind of call to qualify the address.
>>
>> Iow: a slow path call with the address would return flags on whether
>> iowrite() should do a real io, or a IOoHC.
>>
>
> Yes, it could work, though we'd need somewhere to stow this
> information. IIRC Arnd suggested a bit from the address itself.
>
Yeah, exactly. I think MMIO is particularly challenging because I don't
know if there are any bits left to use. But like I said, its a problem
for another day IMO.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2009-08-18 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A8A67ED0200005A000528F5@sinclair.provo.novell.com>
2009-08-18 12:36 ` [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model Gregory Haskins
2009-08-18 12:38 ` Avi Kivity
2009-08-18 13:19 ` Gregory Haskins [this message]
2009-08-18 13:47 ` 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=4A8AAA67.8060602@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=GHaskins@novell.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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 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.