* Xen 4.4 development update -- RFC for feature freeze timeline
@ 2013-09-26 16:47 George Dunlap
2013-09-26 17:24 ` Dario Faggioli
` (4 more replies)
0 siblings, 5 replies; 13+ messages in thread
From: George Dunlap @ 2013-09-26 16:47 UTC (permalink / raw)
To: xen-devel
This information will be mirrored on the Xen 4.4 Roadmap wiki page:
http://wiki.xen.org/wiki/Xen_Roadmap/4.4
= Timeline (RFC!!) =
Here is our current timeline based on a 6-month release:
* Feature freeze: 18 October 2013
* Code freezing point: 8 November 2013
* First RC: 26 November 2013
* Release: 21 January 2014
I've been going through the list and chatting with different
developers, and it seems like there are a number of features in
development that are close to being done, but not quite: they have a
fairly high probability of missing the 18 Oct window, but a pretty
decent chance of making the window if it were extended for a month.
Here are the lists:
Things which will probably make it by 18 Oct:
* Multi-vector MSI (done)
* Improved spice support in libxl (done)
* PVH for domUs
* Non-udev scripts for driver domains
* A raft of fixes from Coverity reports
Additional things which are likely to make it if we extend a month (18
Nov):
* NUMA Memory migration
* Per-vcpu NUMA affinity
* PV NUMA interface
* ARM guest migration
* USB hotplug for libxl
Other things that are a possibility if we slip a month but definitely
not if we stick with the original schedule:
* qemu-xen stubdomains (either Linux or rump kernel / BSD libc)
* Event channel scalability
Obviously there is no guarantee for any of these that a month will
suffice; developers are notoriously bad at estimation and generally
think they can do absolutely anything in 2-3 months.
Nonetheless, it does seem likely that delaying for a month may allow a
significant number of important features to get in.
Any thoughts?
Last updated: 26 September 2016
== Completed ==
* Multi-vector PCI MSI (Hypervisor side)
* Improved Spice support on libxl
- Added Spice vdagent support
- Added Spice clipboard sharing support
== Open ==
* xend still in tree (x)
- xl list -l on a dom0-only system
- xl list -l doesn't contain tty console port
- xl Alternate transport support for migration
- xl PVSCSI support
- xl PVUSB support
* qemu-upstream not freeing pirq
> http://www.gossamer-threads.com/lists/xen/devel/281498
status: patches posted, tested-and-acked
* Race in PV shutdown between tool detection and shutdown watch
> http://www.gossamer-threads.com/lists/xen/devel/282467
> Nothing to do with ACPI
status: Probably a bug in Linux xen drivers
* credit scheduler doesn't update other fields when tslice updated from sysctl
> Reported by Luwei Cheng <lwcheng@cs.hku.hk>
> http://bugs.xenproject.org/xen/bug/16
* Supposed regression from a3513737 ("x86: allow guest to set/clear
> MSI-X mask bit (try 2)"), as per
> http://lists.xenproject.org/archives/html/xen-devel/2013-09/msg01589.html.
== Backlog ==
=== Testing coverage ===
* new libxl w/ previous versions of xl
@IanJ
* Host S3 suspend
@bguthro, @dariof
* Default [example] XSM policy
@Stefano to ask Daniel D
* Xen on ARM
# hardware
@ianc
emulator: @stefano to think about it
* Storage driver domains
@roger
* HVM pci passthrough
@anthony
* PV pce passthrough
@konrad (or @george if he gets to it first)
* Network driver domains
@George
* Nested virt?
@intel (chased by George)
* Fix SRIOV test (chase intel)
@ianj
* Fix bisector to e-mail blame-worthy parties
@ianj
* Fix xl shutdown
@ianj
* stub domains
@athony
* performance benchmarks
@dario
=== Clean-ups ===
* Polish up xenbugtool
owner: wei.liu2@citrix.com
* ACPI WAET table vs RTC emulation mode
owner: jan@suse
prognosis: ?
> An overly simplified fix was posted a while ago
> (http://lists.xenproject.org/archives/html/xen-devel/2013-07/msg00122.html),
> but Tim's objection is rather valid. I can't, however, estimate
> if/when I would find time to learn what tools side changes are
> necessary to accommodate a new HVM param, and hence this is
> currently stalled. The current solution (as of 3fa7fb8b ["x86/HVM:
> RTC code must be in line with WAET flags passed by hvmloader"])
> isn't desirable to be kept for 4.4.
* Sort out better memory / ballooning / dom0 autoballooning thing
> Don't forget NUMA angle
- Inaccurate / incomplete info from HV
* Implement Xen hypervisor dmesg log entry timestamps
> https://xenorg.uservoice.com/forums/172169-xen-development/suggestions/3924048-implement-xen-hypervisor-dmesg-log-entry-timestamp
> Request seems to be for a shorter stamp (seconds-only, rather than full date)
* Make network driver domains easier to set up / more useful
- Make it easy to make a device assignable (in discussion)
- Automatically start/shutdown (xendomains?)
- Pause booting of other domains until network driver domain is up (necessary?)
* libxl: More fine-grained control over when to pass through a device
> Some IOMMUs are secure; some are merely functional, some are not present.
> Allow the adminitrator to set the default
* xl does not handle migrate interruption gracefully
> If you start a localhost migrate, and press "Ctrl-C" in the middle,
> you get two hung domains
* libxl / xl does not handle failure of remote qemu gracefully
> Easiest way to reproduce:
> - set "vncunused=0" and do a local migrate
> - The "remote" qemu will fail because the vnc port is in use
> The failure isn't the problem, but everything being stuck afterwards is
* mac address changes on reboot if not specified in config file
> Needs a robust way to "add" to the config
* qxl
> http://bugs.xenproject.org/xen/bug/11
- Uninitialized struct element in qemu
- Revert 5479961 to re-enable qxl in xl,libxl
- Option in Xen top-level to enable qxl support in qemu tree
- Fix sse2 MMIO issue
- make word size arbitrary
* libxl config file
* libxl: Don't use RAW format for "URL"-based qdisks (e.g., rbd:rbd/foo.img)
- Figure out whether to use a generic URL or have a specific type for each one
- Check existence of disk file for all RAW
* acpi-related xenstore entries not propagated on migrate
> http://www.gossamer-threads.com/lists/xen/devel/282466
> Only used by hvmloader; only a clean-up, not a bug.
=== Big ticket items ===
* NUMA Memory migration
owner: dario@citrix
status: in progress
* Event channel scalability (FIFO event channels)
owner: david@citrix
status: RFC v3 posted
Increase limit on event channels (currently 1024 for 32-bit guests,
4096 for 64-bit guests)
* PVH mode (w/ Linux)
owner: mukesh@oracle, george@citrix
status (Linux): Acked, waiting for ABI to be nailed down
status (Xen): v12 posted
* ARM stuff: ??
* Meta: PVIO NUMA improvements
- NUMA affinity for vcpus
owner: Dario
status: in progress
- PV guest NUMA interface
owner: Elena
status: v2 posted
- Sensible dom0 NUMA layout
- Toolstack pinning backend thread / virq to appropraite d0 vcpu
- NUMA-aware ballooning
owner: Li Yechen
status: in progress
* xl migrate transport improvements
owner: None
> See discussion here: http://bugs.xenproject.org/xen/bug/19
- Option to connect over a plain TCP socket rather than ssh
- xl-migrate-recieve suitable for running in inetd
- option for above to redirect log output somewhere useful
- Documentation for setting up alternate transports
* HVM guest NUMA
owner: Matt Wilson@amazon
status: in progress (?)
* qemu-upstream stubdom, Linux
owner: anthony@citrix
status: in progress
prognosis: ?
qemu-upstream needs a more fully-featured libc than exists in
mini-os. Either work on a minimalist linux-based stubdom with
glibc, or port one of the BSD libcs to minios.
* qemu-upstream stubdom, BSD libc
prognosis: ?
owner: ianj@citrix
* Network performance improvements
owner: wei@citrix
* Disk performance improvements
* Xen EFI feature: Xen can boot from grub.efi
owner: Daniel Kiper
status: in progress
* libvirt/libxl integration (external)
> need a status update
- owner: jfehlig@suse, dario@citrix
* Default to credit2
status: Probably not for 4.4
- cpu pinning
- NUMA affinity
- cpu "reservation"
* xenperf
prognosis: ?
Owner: Boris Otovsky
status: v2 patches posted
* blktap3
owner: thanos@citrix
status: on hold pending XenServer decision
* Nested virtualization on Intel
* Nested virtualization on AMD
* xl USB pass-through for HVM guests using Qemu USB emulation
prognosis: Good if extended
owner: George
status: v6 patch series posted
* libxl: Spice usbredirection support for upstream qemu
owner: fabio@M2R
status: I'll post new patch version shortly
* libxl: usb2 and usb3 controller support for upstream qemu
owner: fabio@M2R
status: patch v5 posted, tested and working, awaiting reviews
* Rationalized backend scripts
owner: roger@citrix
status: patches posted
* Scripts for driver domains (depends on backend scripts)
owner: roger@citrix
status: Patches posted (?)
prognosis: good
* Multi-vector PCI MSI (upstream Linux)
owner: konrad@oracle
* xl: passing more defaults in configuration in xl.conf
owner: ?
There are a number of options for which it might be useful to pass a
default in xl.conf. For example, if we could have a default
"backend" parameter for vifs, then it would be easy to switch back
and forth between a backend in a driver domain and a backend in dom0.
* xl PVUSB pass-through for PV guests
* xl PVUSB pass-through for HVM guests
owner: George
status: ?
xm/xend supports PVUSB pass-through to guests with PVUSB drivers
(both PV and HVM guests).
- port the xm/xend functionality to xl.
- this PVUSB feature does not require support or emulation from Qemu.
- upstream the Linux frontend/backend drivers. Current
work-in-progress versions are in Konrad's git tree.
- James Harper's GPLPV drivers for Windows include PVUSB frontend drivers.
* Guest EFI booting
- status: tianocore in-tree, some build problems.
Needs new owner.
* Xen EFI feature: pvops dom0 able to make use of EFI run-time
services (external)
owner: Daniel Kiper
status: Just begun
* New kexec implementation
owner: dvrabel@citrix
status: v7 posted, only minor updates expected
=== Wishlist / someday ===
* Make storage migration possible
owner: ?
status: none
There needs to be a way, either via command-line or via some hooks,
that someone can build a "storage migration" feature on top of libxl
or xl.
* Full-VM snapshotting
owner: ?
status: none
Have a way of coordinating the taking and restoring of VM memory and
disk snapshots. This would involve some investigation into the best
way to accomplish this.
* VM Cloning
owner: ?
status: none
Again, a way of coordinating the memory and disk aspects. Research
into the best way to do this would probably go along with the
snapshotting feature.
* xl vm-{export,import}
owner: ?
status: none
Allow xl to import and export VMs to other formats; particularly
ovf, perhaps the XenServer format, or more.
* Memory: Replace PoD with paging mechanism
owner: george@citrix
status: none
* PV audio (audio for stubdom qemu)
owner: stefano.panella@citrix
status: ?
* Wait queues for mm
> Needed for more advanced paging schemes
owner: ?
status: Draft posted Feb 2012; more work to do.
* V4V: Inter-domain communication
owner (Xen): dominic.curran@citrix.com
status (Xen): patches submitted
owner (Linux driver): stefano.panella@citrix
status (Linux driver): in progress
* Serial console improvements
owner: ?
status: Stalled (see below)
-xHCI debug port (Needs hardware)
-Firewire (needs hardware)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
@ 2013-09-26 17:24 ` Dario Faggioli
2013-09-27 6:21 ` Elena Ufimtseva
2013-09-27 7:38 ` Jan Beulich
` (3 subsequent siblings)
4 siblings, 1 reply; 13+ messages in thread
From: Dario Faggioli @ 2013-09-26 17:24 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1513 bytes --]
On gio, 2013-09-26 at 17:47 +0100, George Dunlap wrote:
> Additional things which are likely to make it if we extend a month (18
> Nov):
>
> * NUMA Memory migration
>
Yep, I confirm: 18 Nov => probable. 18 Oct => no way. :-(
> * Per-vcpu NUMA affinity
>
This may make it by 18 Oct too. 18 Nov, I'm positive it'll be in.
> * PV NUMA interface
>
It's worth wait for Elena to comment on this, but (as said on IRC) I'm
quite sure there's no way this can make it by 18 Oct.
> Other things that are a possibility if we slip a month but definitely
> not if we stick with the original schedule:
>
> * qemu-xen stubdomains (either Linux or rump kernel / BSD libc)
>
Which would be something really cool to have on the release notes,
especially the rump kernel variant. ;-P
> Nonetheless, it does seem likely that delaying for a month may allow a
> significant number of important features to get in.
>
> Any thoughts?
>
+1 for delaying 1 month.
I think it's probably worth to mention that we have LinuxConEU and
XenSummit coming (and just had LinuxConNA), for which people need to
prepare and attend, which would probably mean even less
developing/reviewing time for getting stuff in by 18 Oct.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-26 17:24 ` Dario Faggioli
@ 2013-09-27 6:21 ` Elena Ufimtseva
0 siblings, 0 replies; 13+ messages in thread
From: Elena Ufimtseva @ 2013-09-27 6:21 UTC (permalink / raw)
To: Dario Faggioli; +Cc: George Dunlap, xen-devel
On Thu, Sep 26, 2013 at 1:24 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On gio, 2013-09-26 at 17:47 +0100, George Dunlap wrote:
>> Additional things which are likely to make it if we extend a month (18
>> Nov):
>>
>> * NUMA Memory migration
>>
> Yep, I confirm: 18 Nov => probable. 18 Oct => no way. :-(
>
>> * Per-vcpu NUMA affinity
>>
> This may make it by 18 Oct too. 18 Nov, I'm positive it'll be in.
>
>> * PV NUMA interface
>>
> It's worth wait for Elena to comment on this, but (as said on IRC) I'm
> quite sure there's no way this can make it by 18 Oct.
I agree, taking into account all other things on the plate.. Nov 18 is
a feasible date.
>
>> Other things that are a possibility if we slip a month but definitely
>> not if we stick with the original schedule:
>>
>> * qemu-xen stubdomains (either Linux or rump kernel / BSD libc)
>>
> Which would be something really cool to have on the release notes,
> especially the rump kernel variant. ;-P
>
>> Nonetheless, it does seem likely that delaying for a month may allow a
>> significant number of important features to get in.
>>
>> Any thoughts?
>>
> +1 for delaying 1 month.
>
> I think it's probably worth to mention that we have LinuxConEU and
> XenSummit coming (and just had LinuxConNA), for which people need to
> prepare and attend, which would probably mean even less
> developing/reviewing time for getting stuff in by 18 Oct.
>
> Regards,
> Dario
>
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
Elena
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
2013-09-26 17:24 ` Dario Faggioli
@ 2013-09-27 7:38 ` Jan Beulich
2013-09-27 9:37 ` David Vrabel
2013-09-27 7:41 ` Jan Beulich
` (2 subsequent siblings)
4 siblings, 1 reply; 13+ messages in thread
From: Jan Beulich @ 2013-09-27 7:38 UTC (permalink / raw)
To: David Vrabel, George Dunlap; +Cc: xen-devel
>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
> * Event channel scalability
I don't recall there having been significant change requests to the
last posting - David, what's your estimation here?
Jan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
2013-09-26 17:24 ` Dario Faggioli
2013-09-27 7:38 ` Jan Beulich
@ 2013-09-27 7:41 ` Jan Beulich
2013-10-04 17:36 ` George Dunlap
2013-09-27 10:21 ` Stefano Stabellini
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
4 siblings, 1 reply; 13+ messages in thread
From: Jan Beulich @ 2013-09-27 7:41 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
> Nonetheless, it does seem likely that delaying for a month may allow a
> significant number of important features to get in.
>
> Any thoughts?
I'm in favor of pushing back by a month as long as this allows at
least a fair share of the listed pending things to go in. An
alternative would be a weak feature freeze (no new features
except for a well defined set) on the original date, but that would
certainly undermine the stabilizing phase to some degree.
Jan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-27 7:38 ` Jan Beulich
@ 2013-09-27 9:37 ` David Vrabel
2013-09-27 9:51 ` Jan Beulich
0 siblings, 1 reply; 13+ messages in thread
From: David Vrabel @ 2013-09-27 9:37 UTC (permalink / raw)
To: Jan Beulich; +Cc: George Dunlap, xen-devel
On 27/09/13 08:38, Jan Beulich wrote:
>>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>> * Event channel scalability
>
> I don't recall there having been significant change requests to the
> last posting - David, what's your estimation here?
The hypervisor and toolstack changes are now done. There's one
remaining issue with the Linux side.
Should be easily done before Oct 18.
I can repost the Xen series now if people would prefer an earlier review.
David
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-27 9:37 ` David Vrabel
@ 2013-09-27 9:51 ` Jan Beulich
0 siblings, 0 replies; 13+ messages in thread
From: Jan Beulich @ 2013-09-27 9:51 UTC (permalink / raw)
To: David Vrabel; +Cc: George Dunlap, xen-devel
>>> On 27.09.13 at 11:37, David Vrabel <david.vrabel@citrix.com> wrote:
> On 27/09/13 08:38, Jan Beulich wrote:
>>>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>>> * Event channel scalability
>>
>> I don't recall there having been significant change requests to the
>> last posting - David, what's your estimation here?
>
> The hypervisor and toolstack changes are now done. There's one
> remaining issue with the Linux side.
>
> Should be easily done before Oct 18.
>
> I can repost the Xen series now if people would prefer an earlier review.
Unless the Linux side issue is risking to need an interface change
to deal with, I'd recommend doing so, as in that case the
hypervisor/tools side could then already go in (be sure to Cc
Keir, as he'll need to ack most of the hypervisor side; not sure
whether you got tools side acks already).
Jan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
` (2 preceding siblings ...)
2013-09-27 7:41 ` Jan Beulich
@ 2013-09-27 10:21 ` Stefano Stabellini
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
4 siblings, 0 replies; 13+ messages in thread
From: Stefano Stabellini @ 2013-09-27 10:21 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
On Thu, 26 Sep 2013, George Dunlap wrote:
> Additional things which are likely to make it if we extend a month (18
> Nov):
>
> * NUMA Memory migration
> * Per-vcpu NUMA affinity
> * PV NUMA interface
> * ARM guest migration
> * USB hotplug for libxl
* new hypercalls for SWIOTLB on ARM
> Nonetheless, it does seem likely that delaying for a month may allow a
> significant number of important features to get in.
>
> Any thoughts?
+ 1 for delaying by one month
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update -- RFC for feature freeze timeline
2013-09-27 7:41 ` Jan Beulich
@ 2013-10-04 17:36 ` George Dunlap
0 siblings, 0 replies; 13+ messages in thread
From: George Dunlap @ 2013-10-04 17:36 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
On 27/09/13 08:41, Jan Beulich wrote:
>>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>> Nonetheless, it does seem likely that delaying for a month may allow a
>> significant number of important features to get in.
>>
>> Any thoughts?
> I'm in favor of pushing back by a month as long as this allows at
> least a fair share of the listed pending things to go in.
Well it's really hard to say -- back in January I said that the USB
hot-plug series was basically ready to go in, but it wasn't ready by
April when we had the feature freeze. Sometimes I feel like I'm reading
tea leaves here. :-) All we can do is make our best stab at things, and
then go back and see how we did.
> An
> alternative would be a weak feature freeze (no new features
> except for a well defined set) on the original date, but that would
> certainly undermine the stabilizing phase to some degree.
Well in theory it would allow "frozen" parts of the code (those not
touched by the well-defined set of features) to start stabilizing while
we are still working on non-frozen parts. But the non-frozen parts
still need to be stabilized, and the features we are talking about
including are pretty big and will need a decent amount of time for
stabilization; so I don't really see how doing a partial freeze is going
to really help that much.
-George
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update, qemu pci hole start address
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
` (3 preceding siblings ...)
2013-09-27 10:21 ` Stefano Stabellini
@ 2013-10-08 18:05 ` Pasi Kärkkäinen
2013-10-08 18:13 ` Pasi Kärkkäinen
4 siblings, 1 reply; 13+ messages in thread
From: Pasi Kärkkäinen @ 2013-10-08 18:05 UTC (permalink / raw)
To: George Dunlap; +Cc: Stefano Stabellini, xen-devel
On Thu, Sep 26, 2013 at 05:47:40PM +0100, George Dunlap wrote:
>
http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
"quick" workaround was proposed for Xen 4.3 release, and the "proper" solution
to be done later for Xen 4.4. Is that still the case? Does this issue still need to be resolved?
Quote from the above email/url, Stefano writing:
"this is what I would do:
1) modify upstream QEMU to start the PCI hole at 0xe0000000, to match
qemu-xen-unstable in terms of configuration and not to introduce any
regressions. Do this for the Xen 4.3 release.
2) for Xen 4.4 rework the two patches above and improve
i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
enough, it also needs to be able to resize the system memory region
(xen.ram) to make room for the bigger pci_hole"
Thanks,
-- Pasi
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update, qemu pci hole start address
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
@ 2013-10-08 18:13 ` Pasi Kärkkäinen
2013-10-09 10:39 ` George Dunlap
0 siblings, 1 reply; 13+ messages in thread
From: Pasi Kärkkäinen @ 2013-10-08 18:13 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel, Hanweidong, Stefano Stabellini
On Tue, Oct 08, 2013 at 09:05:55PM +0300, Pasi Kärkkäinen wrote:
> On Thu, Sep 26, 2013 at 05:47:40PM +0100, George Dunlap wrote:
> >
>
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
>
> "quick" workaround was proposed for Xen 4.3 release, and the "proper" solution
> to be done later for Xen 4.4. Is that still the case? Does this issue still need to be resolved?
>
> Quote from the above email/url, Stefano writing:
>
> "this is what I would do:
>
> 1) modify upstream QEMU to start the PCI hole at 0xe0000000, to match
> qemu-xen-unstable in terms of configuration and not to introduce any
> regressions. Do this for the Xen 4.3 release.
>
> 2) for Xen 4.4 rework the two patches above and improve
> i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
> enough, it also needs to be able to resize the system memory region
> (xen.ram) to make room for the bigger pci_hole"
>
>
Hmm, or maybe this series fixed the issue already properly for Xen 4.3.0?
"[PATCH v5 0/8] Relocate devices rather than memory for qemu-xen":
http://lists.xen.org/archives/html/xen-devel/2013-06/msg02185.html
Hanweidong: Can you confirm this issue was already fixed for you in Xen 4.3.0 ?
Thanks,
-- Pasi
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update, qemu pci hole start address
2013-10-08 18:13 ` Pasi Kärkkäinen
@ 2013-10-09 10:39 ` George Dunlap
2013-11-11 18:17 ` Pasi Kärkkäinen
0 siblings, 1 reply; 13+ messages in thread
From: George Dunlap @ 2013-10-09 10:39 UTC (permalink / raw)
To: Pasi Kärkkäinen; +Cc: xen-devel, Hanweidong, Stefano Stabellini
On 08/10/13 19:13, Pasi Kärkkäinen wrote:
> On Tue, Oct 08, 2013 at 09:05:55PM +0300, Pasi Kärkkäinen wrote:
>> On Thu, Sep 26, 2013 at 05:47:40PM +0100, George Dunlap wrote:
>> http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
>>
>> "quick" workaround was proposed for Xen 4.3 release, and the "proper" solution
>> to be done later for Xen 4.4. Is that still the case? Does this issue still need to be resolved?
>>
>> Quote from the above email/url, Stefano writing:
>>
>> "this is what I would do:
>>
>> 1) modify upstream QEMU to start the PCI hole at 0xe0000000, to match
>> qemu-xen-unstable in terms of configuration and not to introduce any
>> regressions. Do this for the Xen 4.3 release.
>>
>> 2) for Xen 4.4 rework the two patches above and improve
>> i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
>> enough, it also needs to be able to resize the system memory region
>> (xen.ram) to make room for the bigger pci_hole"
>>
>>
> Hmm, or maybe this series fixed the issue already properly for Xen 4.3.0?
No, this series is still a work-around; see 8/8 of that series: "It's
too late in the release to do a proper fix, so we try to do damage
control." It is fairly likely that there are OS / device combinations
that currently will not work for PCI pass-through, because either the
OS, the driver, or the device won't work when relocated into 64-bit PCI
space.
(I think the problem Gordan has been working on might be related, but
I'm not sure.)
So yes, good catch -- there should still be an outstanding issue related
to qemu-xen.
-George
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Xen 4.4 development update, qemu pci hole start address
2013-10-09 10:39 ` George Dunlap
@ 2013-11-11 18:17 ` Pasi Kärkkäinen
0 siblings, 0 replies; 13+ messages in thread
From: Pasi Kärkkäinen @ 2013-11-11 18:17 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel, Hanweidong, Stefano Stabellini
On Wed, Oct 09, 2013 at 11:39:52AM +0100, George Dunlap wrote:
> >>
> >Hmm, or maybe this series fixed the issue already properly for Xen 4.3.0?
>
> No, this series is still a work-around; see 8/8 of that series:
> "It's too late in the release to do a proper fix, so we try to do
> damage control." It is fairly likely that there are OS / device
> combinations that currently will not work for PCI pass-through,
> because either the OS, the driver, or the device won't work when
> relocated into 64-bit PCI space.
>
> (I think the problem Gordan has been working on might be related,
> but I'm not sure.)
>
> So yes, good catch -- there should still be an outstanding issue
> related to qemu-xen.
>
Hello,
I think this issue wasn't added to the Xen status emails / backlog yet?
Thanks,
-- Pasi
> -George
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2013-11-11 18:17 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
2013-09-26 17:24 ` Dario Faggioli
2013-09-27 6:21 ` Elena Ufimtseva
2013-09-27 7:38 ` Jan Beulich
2013-09-27 9:37 ` David Vrabel
2013-09-27 9:51 ` Jan Beulich
2013-09-27 7:41 ` Jan Beulich
2013-10-04 17:36 ` George Dunlap
2013-09-27 10:21 ` Stefano Stabellini
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
2013-10-08 18:13 ` Pasi Kärkkäinen
2013-10-09 10:39 ` George Dunlap
2013-11-11 18:17 ` Pasi Kärkkäinen
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.