From: "Jim C. Brown" <jma5@umd.edu>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI access virtualization
Date: Thu, 5 Jan 2006 16:13:11 -0500 [thread overview]
Message-ID: <20060105211311.GA20203@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200601051810.54954.paul@codesourcery.com>
On Thu, Jan 05, 2006 at 06:10:54PM +0000, Paul Brook wrote:
> On Thursday 05 January 2006 17:40, Mark Williamson wrote:
> > > - IRQ sharing. Sharing host IRQs between native and virtualized devices
> > > is hard because the host needs to ack the interrupt in the IRQ handler,
> > > but doesn't really know how to do that until after it's run the guest to
> > > see what that does.
> >
> > Could maybe have the (inevitable) kernel portion of the code grab the
> > interrupt, and not ack it until userspace does an ioctl on a special file
> > (or something like that?). There are patches floating around for userspace
> > IRQ handling, so I guess that could work.
>
> This still requires cooperation from both sides (ie. both the host and guest
> drivers).
>
This would be a lot easier if linux supported user-space device drivers..
and I believe work is being done in that area.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2006-01-05 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 10:14 [Qemu-devel] PCI access virtualization Michael Renzmann
2006-01-05 14:25 ` Paul Brook
2006-01-05 17:40 ` Mark Williamson
2006-01-05 18:10 ` Paul Brook
2006-01-05 21:13 ` Jim C. Brown [this message]
2006-01-06 1:54 ` Mark Williamson
2006-01-06 13:27 ` Paul Brook
2006-01-06 14:23 ` Mark Williamson
2006-01-05 16:25 ` Mark Williamson
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=20060105211311.GA20203@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=paul@codesourcery.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).