From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andy Burns <xen.lists@burns.me.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: 2.6.30 Xen merge plan (what's in xen.git)
Date: Sun, 29 Mar 2009 13:51:29 -0700 [thread overview]
Message-ID: <49CFDF51.2010706@goop.org> (raw)
In-Reply-To: <b4057d410903291315j2f4d5170red569e9d3534078c@mail.gmail.com>
Andy Burns wrote:
> 2009/3/24 Jeremy Fitzhardinge <jeremy@goop.org>:
>
>
>> push2/xen/dom0/apic
>> push2/xen/dom0/pci
>>
>
> Does it mean that if these patchsets make it into 2.6.30 there will be
> paravirt_ops dom0 that supports PCI passthrough?
>
No, those are just the changes necessary to have native device drivers
in dom0 work at all. In fact, I'm not proposing any backend device
support for mainline in this merge window, so you'll still need some out
of tree changes to get a useful system. But these changes do have a
fair amount in common with what's needed for pci passthrough, so there
is some progress (albeit abstract).
J
prev parent reply other threads:[~2009-03-29 20:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:17 2.6.30 Xen merge plan (what's in xen.git) Jeremy Fitzhardinge
2009-03-24 17:17 ` Jeremy Fitzhardinge
2009-03-24 17:36 ` [GIT PULL] xen.git 2.6.30: push2/x86/paravirt: preemption in lazy mmu updates Jeremy Fitzhardinge
2009-03-24 17:36 ` Jeremy Fitzhardinge
2009-03-24 17:37 ` [GIT PULL] xen.git 2.6.30: core Xen updates Jeremy Fitzhardinge
2009-03-24 17:37 ` Jeremy Fitzhardinge
2009-03-24 17:39 ` [GIT PULL] xen.git 2.6.30: usermode control interfaces Jeremy Fitzhardinge
2009-03-24 17:39 ` Jeremy Fitzhardinge
2009-03-24 17:40 ` [GIT PULL] xen.git 2.6.30: xen dom0 core support Jeremy Fitzhardinge
2009-03-24 17:40 ` Jeremy Fitzhardinge
2009-03-24 17:42 ` [GIT PULL] xen.git 2.6.30: xen dom0 apic changes Jeremy Fitzhardinge
2009-03-24 17:42 ` Jeremy Fitzhardinge
2009-03-24 17:43 ` [GIT PULL] xen.git 2.6.30: xen dom0 PCI device support Jeremy Fitzhardinge
2009-03-24 17:43 ` Jeremy Fitzhardinge
2009-03-24 17:48 ` 2.6.30 Xen merge plan (what's in xen.git) Ingo Molnar
2009-03-24 17:48 ` Ingo Molnar
2009-03-24 18:08 ` Jeremy Fitzhardinge
2009-03-24 18:08 ` Jeremy Fitzhardinge
2009-03-24 23:05 ` H. Peter Anvin
2009-03-24 23:28 ` H. Peter Anvin
2009-03-25 5:49 ` Jeremy Fitzhardinge
2009-03-25 5:49 ` Jeremy Fitzhardinge
2009-03-29 15:58 ` Jeremy Fitzhardinge
2009-03-29 15:58 ` Jeremy Fitzhardinge
2009-03-29 20:15 ` Andy Burns
2009-03-29 20:51 ` Jeremy Fitzhardinge [this message]
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=49CFDF51.2010706@goop.org \
--to=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen.lists@burns.me.uk \
/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.