flight 31716 linux-3.10 real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31716/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install fail REGR. vs. 26303
Tests which are failin
flight 31694 xen-4.3-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31694/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install fail REGR. vs. 31536
Tests which did n
flight 31691 linux-next real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31691/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-rumpuserxen-amd64 8 guest-start fail baseline untested
test-amd64-amd64-xl-sedf 15
On Fri, 21 Nov 2014, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 21, 2014 at 08:51:43PM +0100, Thomas Gleixner wrote:
> > On Fri, 21 Nov 2014, Linus Torvalds wrote:
> > > Here's the simplified end result. Again, this is TOTALLY UNTESTED. I
> > > compiled it and verified that the code generation loo
flight 31686 qemu-mainline real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31686/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-pair17 guest-migrate/src_host/dst_host fail like 31651
Tests which did not succeed,
flight 31683 linux-linus real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31683/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 8 guest-start fail REGR. vs. 31241
test-amd64-amd64-rump
On Fri, Nov 21, 2014 at 08:51:43PM +0100, Thomas Gleixner wrote:
> On Fri, 21 Nov 2014, Linus Torvalds wrote:
> > Here's the simplified end result. Again, this is TOTALLY UNTESTED. I
> > compiled it and verified that the code generation looks like what I'd
> > have expected, but that's literally it
As commit 0a9fd0152929db372ff61b0d6c280fdd34ae8bdb
'xen/pciback: Document the entry points for 'pcistub_put_pci_dev''
explained there are four entry points in this function.
Two of them are when the user fiddles in the SysFS to
unbind a device which might be in use by a guest or not.
Both 'unbind'
The commit "xen/pciback: Don't deadlock when unbinding." was using
the version of pci_reset_function which would lock the device lock.
That is no good as we can dead-lock. As such we swapped to using
the lock-less version and requiring that the callers
of 'pcistub_put_pci_dev' take the device lock.
A little cleanup. No functional difference.
Reviewed-by: Boris Ostrovsky
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/xen/xen-pciback/pci_stub.c
b/drivers/xen/xen-pc
We had been printing it only if the device was built with
debug enabled. But this information is useful in the field
to troubleshoot.
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: David Vrabel
---
drivers/xen/xen-pciback/xenbus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
Hey,
The last time I posted these patches: https://lkml.org/lkml/2014/7/8/533
was so long ago that I don't even remember most comments. The only
one that stuck in mind was David's recommendation to add a new PCI API
call and use that. See patch #6 and #7.
The original posting (v3) had an extra p
We have the pci_load_and_free_saved_state, and pci_store_saved_state
but are missing the functionality to just load the state
multiple times in the PCI device without having to free/save
the state.
This patch makes it possible to use this function.
CC: Bjorn Helgaas
Signed-off-by: Konrad Rzeszut
Instead of open-coding it in drivers that want to double check
that their functions are indeed holding the device lock.
Signed-off-by: Konrad Rzeszutek Wilk
Suggested-by: David Vrabel
Acked-by: Greg Kroah-Hartman
---
drivers/xen/xen-pciback/pci_stub.c | 2 +-
include/linux/device.h
Cleanup the function a bit - also include the id of the
domain that is using the device.
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: David Vrabel
---
drivers/xen/xen-pciback/pci_stub.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/xen/xen-pciback/p
On Thu, Nov 06, 2014 at 03:05:51PM +, Jan Beulich wrote:
> When a PF driver unloads, it may find it necessary to leave the VFs
> around simply because of pciback having marked them as assigned to a
> guest. Utilize a suitable notification to let go of the VFs, thus
> allowing the PF to go back
flight 31681 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31681/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 7 xen-boot/src_host fail REGR. vs. 31659
Regressions which ar
On Nov 21, 2:57pm, "Dr. Greg Wettstein" wrote:
} Subject: [Xen-devel] Q77 IGD instantly crashes on xen-pciback bind.
> Hi, hope the week is ending well for everyone.
As I was walking out the door I remembered I had been delinquent with
information. The dom0 kernel is 32-bit 3.14.22 straight fro
Hi, hope the week is ending well for everyone.
As readers of the list may remember we've kept the ATI primary adapter
passthrough patches current for qemu-traditional on Xen for a number
of years. Our 'run-passthrough' utility for binding/unbind devices
and running a Windows guest with passthroug
On Fri, Nov 21, 2014 at 03:01:58PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 21, 2014 at 03:06:42PM +, Wei Liu wrote:
> > Hi all
> >
> > This patch series implements virtual NUMA support for both PV and HVM guest.
> > That is, admin can configure via libxl what virtual NUMA topology th
On 11/21/2014 06:12 AM, Ian Campbell wrote:
On Fri, 2014-11-21 at 11:03 +, Ian Campbell wrote:
http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about
various dynamic thresholds for growing and shrinking the heap. My guess
is that we are bouncing up and down over some threshold
On 11/21/2014 06:03 AM, Ian Campbell wrote:
So here's what happens now.
1. Starts up tiny
2. reboot: leak
3. reboot: freed (process larger, but the delta is all/mostly shared pages)
4. reboot: leak
5. reboot: freed
etc..
WTF, how very strange!
:-)
--- reboot domu ---
root@xen:~/xen-pkgs#
On 11/21/2014 07:32 AM, Ian Campbell wrote:
>From 9f2d8da8264b426f54b92378e9e00973694193d4 Mon Sep 17 00:00:00 2001
From: Ian Campbell
Date: Fri, 21 Nov 2014 14:00:38 +
Subject: [PATCH] libxl: Allow libxl to find pygrub binary.
Specifying an explicit path to pygrub (e.g. BINDIR "/pygrub") o
On Fri, Nov 21, 2014 at 03:06:42PM +, Wei Liu wrote:
> Hi all
>
> This patch series implements virtual NUMA support for both PV and HVM guest.
> That is, admin can configure via libxl what virtual NUMA topology the guest
> sees.
>
> This is the stage 1 (basic vNUMA support) and part of stage
On Fri, Nov 21, 2014 at 03:06:56PM +, Wei Liu wrote:
> Signed-off-by: Wei Liu
> Cc: Jan Beulich
> Cc: George Dunlap
> ---
> tools/firmware/hvmloader/pci.c | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git a/tools/firmware/hvmloader/pci.c b/tools/firmware/hvmloader/pci
flight 31680 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31680/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-amd64-amd64-libvirt 9 guest-start
On Fri, Nov 21, 2014 at 06:48:53PM +, Stefano Stabellini wrote:
> On Fri, 21 Nov 2014, Konrad Rzeszutek Wilk wrote:
> > On Fri, Nov 21, 2014 at 05:11:09PM +, Stefano Stabellini wrote:
> > > The rom is used for pxebooting. We don't need to allow pxebooting from
> > > more than one network ca
On Fri, 21 Nov 2014, Ian Campbell wrote:
An absolute age ago Michael posted a patch to allow pygrub to work with
split-partition layouts (i.e. those where the guests disk cfg refers to
xvda1, xvda2, etc rather than an xvda with a partition table). See
http://lists.xen.org/archives/html/xen-devel
On Fri, 21 Nov 2014, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 21, 2014 at 05:11:09PM +, Stefano Stabellini wrote:
> > The rom is used for pxebooting. We don't need to allow pxebooting from
> > more than one network card. Loading a romfile for every NIC wastes
>
> Why not? Why can't we PXE b
(Followup list trimmed)
On 11/21/2014 12:42 PM, konrad.w...@oracle.com wrote:
= Open =
== Known issues ==
* xc_reserved_device_memory_map in hvmloader to avoid conflicting MMIO/RAM
(good)
RFC v6
Treating pieces as bug-fixes only.
- Tiejun Chen
* PCI passthrough of INTx legacy
On 11/21/2014 01:14 PM, Wei Liu wrote:
> On Fri, Nov 21, 2014 at 01:09:07PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Nov 21, 2014 at 01:04:42PM -0500, Zhigang Wang wrote:
>>> On 11/14/2014 05:22 AM, Ian Campbell wrote:
On Fri, 2014-11-14 at 10:09 +, Wei Liu wrote:
> On Fri, Nov 1
On Fri, Nov 21, 2014 at 01:09:07PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 21, 2014 at 01:04:42PM -0500, Zhigang Wang wrote:
> > On 11/14/2014 05:22 AM, Ian Campbell wrote:
> > > On Fri, 2014-11-14 at 10:09 +, Wei Liu wrote:
> > >> On Fri, Nov 14, 2014 at 09:59:00AM +, Ian Campbel
On Fri, Nov 21, 2014 at 01:04:42PM -0500, Zhigang Wang wrote:
> On 11/14/2014 05:22 AM, Ian Campbell wrote:
> > On Fri, 2014-11-14 at 10:09 +, Wei Liu wrote:
> >> On Fri, Nov 14, 2014 at 09:59:00AM +, Ian Campbell wrote:
> >>> On Wed, 2014-11-12 at 17:04 +, Wei Liu wrote:
> Uncondi
On 11/14/2014 05:22 AM, Ian Campbell wrote:
> On Fri, 2014-11-14 at 10:09 +, Wei Liu wrote:
>> On Fri, Nov 14, 2014 at 09:59:00AM +, Ian Campbell wrote:
>>> On Wed, 2014-11-12 at 17:04 +, Wei Liu wrote:
Unconditionally print out the partial configuration.
>>>
>>> Can you provide an
On Fri, Nov 21, 2014 at 12:54:08PM -0500, Don Slutz wrote:
> On 11/21/14 12:42, konrad.w...@oracle.com wrote:
> >Feature patchsets that did not make it in by today have been put
> >on the deferred list. If you think your feature should make it by Xen 4.5-RC3
> >please make your case.
> >
> >Xen 4.5
On 11/21/14 12:42, konrad.w...@oracle.com wrote:
Feature patchsets that did not make it in by today have been put
on the deferred list. If you think your feature should make it by Xen 4.5-RC3
please make your case.
Xen 4.5-rc2 was out on Monday (11th). There are three known issues, if I have
mis
flight 31747 rumpuserxen real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/31747/
Perfect :-)
All tests in this flight passed
version targeted for testing:
rumpuserxen f6bdde8127b10e2bc3f21549dc9c960672ad7718
baseline version:
rumpuserxen 9716ed62cb1d73254b552e207749
Feature patchsets that did not make it in by today have been put
on the deferred list. If you think your feature should make it by Xen 4.5-RC3
please make your case.
Xen 4.5-rc2 was out on Monday (11th). There are three known issues, if I have
missed one (or more) please respond.
(see 'Known Issu
On Fri, 2014-11-21 at 14:32 +, Ian Campbell wrote:
I've now built and tested this with the 1.2.9 Debian package, works like
a charm...
> From 9f2d8da8264b426f54b92378e9e00973694193d4 Mon Sep 17 00:00:00 2001
> From: Ian Campbell
> Date: Fri, 21 Nov 2014 14:00:38 +
> Subject: [PATCH] libx
On Fri, Nov 21, 2014 at 05:11:09PM +, Stefano Stabellini wrote:
> The rom is used for pxebooting. We don't need to allow pxebooting from
> more than one network card. Loading a romfile for every NIC wastes
Why not? Why can't we PXE boot from each network card?
> memory and as a matter of fac
On Fri, Nov 21, 2014 at 05:03:09PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 16:06, wrote:
> > @@ -747,6 +786,17 @@ long do_memory_op(unsigned long cmd,
> > XEN_GUEST_HANDLE_PARAM(void) arg)
> > return start_extent;
> > args.domain = d;
> >
> > +args.memflags
The rom is used for pxebooting. We don't need to allow pxebooting from
more than one network card. Loading a romfile for every NIC wastes
memory and as a matter of fact breaks configurations with more than 4
NICs as QEMU fails to allocate memory on behalf of the guest.
With this fix, it is possib
On Fri, Nov 21, 2014 at 05:00:05PM +, Stefano Stabellini wrote:
> Hi all,
> I have a couple of small straightforward fixes for swiotlb-xen for 3.19.
>
They look fine to me.
Thanks.
> Cheers,
>
> Stefano
>
>
> Stefano Stabellini (2):
> swiotlb-xen: call xen_dma_sync_single_for_device
On Fri, Nov 21, 2014 at 01:53:32PM -0300, Simon Martin wrote:
> Hello Konrad and Jan,
>
>
> > There was a bug in Xen pcibackend that I thought I upstreamed which could
> > be releated. It was not restoring the right registers to the PCI-device.
>
> > They are attached.
>
> Thanks for the patche
On 11/21/2014 12:09 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Nov 21, 2014 at 01:32:13PM +, Andrew Cooper wrote:
That does look plausibly like it would fix the issue.
However, I can't help but feeing that this is hacking around a broken
patch in the first place.
I cannot think of a reason y
On 21.11.2014 17:59, Ian Campbell wrote:
> On Wed, 2014-11-19 at 11:57 -0700, Xing Lin wrote:
>> Hi Ian,
>>
>>
>> Both of your two points are valid. There is no need to install
>> virt-manager. And the patch to start a qemu process in /etc/init.d/xen
>> seems to be enough for launching instances fr
On Fri, Nov 21, 2014 at 01:32:13PM +, Andrew Cooper wrote:
> On 20/11/14 16:45, Boris Ostrovsky wrote:
> > On 11/20/2014 11:15 AM, Ian Campbell wrote:
> >> On Thu, 2014-11-20 at 16:08 +, Andrew Cooper wrote:
> >>> On 20/11/14 16:00, Ian Campbell wrote:
> On Mon, 2014-11-17 at 15:19 +00
>>> On 21.11.14 at 17:55, wrote:
> Nonetheless I'm all for having a configuration option that would meet
> both present and future need. Do you have anything in mind? Are you
> suggesting we should allow specifying every element in SLIT in xl?
I think that would be desirable.
Jan
_
>>> On 21.11.14 at 16:06, wrote:
> @@ -747,6 +786,17 @@ long do_memory_op(unsigned long cmd,
> XEN_GUEST_HANDLE_PARAM(void) arg)
> return start_extent;
> args.domain = d;
>
> +args.memflags |= MEMF_node(XENMEMF_get_node(reservation.mem_flags));
> +if ( rese
On Thu, Nov 20, 2014 at 03:28:30PM +, Ian Campbell wrote:
> On Wed, 2014-11-19 at 16:25 -0500, Konrad Rzeszutek Wilk wrote:
> > On Wed, Nov 19, 2014 at 11:26:32AM +, Ian Jackson wrote:
> > > Hi Konrad, I have another release ack request:
> > >
> > > Chunyan Liu writes ("[PATCH 0/2 V3] fix
In xen_swiotlb_sync_single we always call xen_dma_sync_single_for_cpu,
even when we should call xen_dma_sync_single_for_device. Fix that.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: sta...@vger.kernel.org
---
drivers/xen/swiotlb-xen.c |2 +-
1 file changed, 1 insertion(+
Hi all,
I have a couple of small straightforward fixes for swiotlb-xen for 3.19.
Cheers,
Stefano
Stefano Stabellini (2):
swiotlb-xen: call xen_dma_sync_single_for_device when appropriate
swiotlb-xen: pass dev_addr to swiotlb_tbl_unmap_single
drivers/xen/swiotlb-xen.c |4 ++--
Need to pass the pointer within the swiotlb internal buffer to the
swiotlb library, that in the case of xen_unmap_single is dev_addr, not
paddr.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: sta...@vger.kernel.org
---
drivers/xen/swiotlb-xen.c |2 +-
1 file changed, 1 inse
On Wed, 2014-11-19 at 11:57 -0700, Xing Lin wrote:
> Hi Ian,
>
>
> Both of your two points are valid. There is no need to install
> virt-manager. And the patch to start a qemu process in /etc/init.d/xen
> seems to be enough for launching instances from horizon. I have
> updated the wiki page. Pl
On Fri, Nov 21, 2014 at 04:42:07PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 17:35, wrote:
> > On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
> >> >>> On 21.11.14 at 16:06, wrote:
> >> > vnuma_vdistances = [10, 30] # optional
> >>
> >> Being optional, would the real distances
Hello Konrad and Jan,
> There was a bug in Xen pcibackend that I thought I upstreamed which could
> be releated. It was not restoring the right registers to the PCI-device.
> They are attached.
Thanks for the patches, however I have been finding some very
interesting things.
I decided to keep
On Fri, Nov 21, 2014 at 04:31:31PM +, Stefano Stabellini wrote:
> On Wed, 12 Nov 2014, Stefano Stabellini wrote:
> > Introduce an arch specific function to find out whether a particular dma
> > mapping operation needs to bounce on the swiotlb buffer.
> >
> > On ARM and ARM64, if the page invol
On Fri, Nov 21, 2014 at 03:55:37PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 16:14, wrote:
> > On Fri, Nov 21, 2014 at 01:03:43PM +0100, Jan Beulich wrote:
> >> >>> On 21.11.14 at 12:50, wrote:
> >> > On November 21, 2014 2:51:33 AM EST, Jan Beulich
> >> > wrote:
> >> > On 20.11.14 at
>>> On 21.11.14 at 17:35, wrote:
> On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
>> >>> On 21.11.14 at 16:06, wrote:
>> > vnuma_vdistances = [10, 30] # optional
>>
>> Being optional, would the real distances be used instead? And what
>
> Default value of [10, 20] will be used.
T
>>> On 21.11.14 at 16:06, wrote:
> Signed-off-by: Elena Ufimsteva
> Signed-off-by: Wei Liu
> Cc: Jan Beulich
> ---
> xen/arch/x86/numa.c | 46 +-
> 1 file changed, 45 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/numa.c b/xen/arch/x86
On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 16:06, wrote:
> > memory = 6000
> > vnuma_memory = [3000, 3000]
>
> So what would
>
> memory = 6000
> vnuma_memory = [3000, 2000]
>
> or
>
> memory = 6000
> vnuma_memory = [3000, 4000]
>
Those are not valid con
Ian Campbell writes ("[PATCH OSSTEST v3 04/15] make-flight: Run a basic test on
each arm platform"):
> Unlike x86 there is enough variation in the ARM platforms that it is
> worth having a basic test on each as part of a standard run. This
> relies on each host having an appropriate platform-$plat
On Wed, 12 Nov 2014, Stefano Stabellini wrote:
> Introduce an arch specific function to find out whether a particular dma
> mapping operation needs to bounce on the swiotlb buffer.
>
> On ARM and ARM64, if the page involved is a foreign page and the device
> is not coherent, we need to bounce beca
Ian Campbell writes ("[PATCH OSSTEST v3 02/15] ts-kernel-build: enable
CONFIG_IKCONFIG{_PROC}"):
> This makes the kernel's .config available in /proc/config.gz and embeds a co\
py
> which can be extracted with linux/scripts/extract-ikconfig (which I've not
> tried, but have no reason to doubt).
A
Ian Campbell writes ("[PATCH OSSTEST v3 01/15] standalone: Introduce
"HostGroups" for use in OSSTEST_CONFIG"):
> This saves repeating identical HostProp and HostFlags for sets of identical
> machines. e.g.
Acked-by: Ian Jackson
___
Xen-devel mailing l
>>> On 21.11.14 at 16:06, wrote:
> memory = 6000
> vnuma_memory = [3000, 3000]
So what would
memory = 6000
vnuma_memory = [3000, 2000]
or
memory = 6000
vnuma_memory = [3000, 4000]
mean? Redundant specification of values is always a problem...
Would be possible to extend "memory" to allow for
On 21/11/14 16:00, Jan Beulich wrote:
On 21.11.14 at 16:48, wrote:
>> On 21/11/14 15:38, Jan Beulich wrote:
>> On 21.11.14 at 16:01, wrote:
On 21/11/14 14:54, Jan Beulich wrote:
On 21.11.14 at 15:39, wrote:
>> Trying to do PCI-passthrough with a 32-bit pv-domain I pass
>>> On 21.11.14 at 16:48, wrote:
> On 21/11/14 15:38, Jan Beulich wrote:
> On 21.11.14 at 16:01, wrote:
>>> On 21/11/14 14:54, Jan Beulich wrote:
>>> On 21.11.14 at 15:39, wrote:
> Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
> wrong device to the domain. The
>>> On 21.11.14 at 16:14, wrote:
> On Fri, Nov 21, 2014 at 01:03:43PM +0100, Jan Beulich wrote:
>> >>> On 21.11.14 at 12:50, wrote:
>> > On November 21, 2014 2:51:33 AM EST, Jan Beulich wrote:
>> > On 20.11.14 at 20:51, wrote:
>> >>> @@ -669,7 +670,7 @@ static void hvm_dirq_assist(struct do
On 21/11/14 15:38, Jan Beulich wrote:
On 21.11.14 at 16:01, wrote:
>> On 21/11/14 14:54, Jan Beulich wrote:
>> On 21.11.14 at 15:39, wrote:
Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
wrong device to the domain. The MMIO address was too large for a
MF
>>> On 21.11.14 at 16:17, wrote:
> On 11/21/2014 03:54 PM, Jan Beulich wrote:
> On 21.11.14 at 15:39, wrote:
>>> Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
>>> wrong device to the domain. The MMIO address was too large for a
>>> MFN of a 32-bit system (it was 3800032000
>>> On 21.11.14 at 16:01, wrote:
> On 21/11/14 14:54, Jan Beulich wrote:
> On 21.11.14 at 15:39, wrote:
>>> Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
>>> wrong device to the domain. The MMIO address was too large for a
>>> MFN of a 32-bit system (it was 38000320-38
This patch includes configuration options parser and documentation.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
docs/man/xl.cfg.pod.5| 32 ++
tools/libxl/xl_cmdimpl.c | 151 ++
2
Signed-off-by: Wei Liu
Cc: Jan Beulich
---
xen/include/public/hvm/hvm_info_table.h | 19 +++
1 file changed, 19 insertions(+)
diff --git a/xen/include/public/hvm/hvm_info_table.h
b/xen/include/public/hvm/hvm_info_table.h
index 36085fa..9d3f218 100644
--- a/xen/include/public/
On 21/11/14 15:04, Juergen Gross wrote:
> On 11/21/2014 03:45 PM, Andrew Cooper wrote:
>> On 21/11/14 14:39, Juergen Gross wrote:
>>> Hi,
>>>
>>> again a fallout from my "linear p2m list" tests:
>>>
>>> Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
>>> wrong device to the domain
On Thu, Nov 20, 2014 at 10:39:32AM +, Stefano Stabellini wrote:
> On Thu, 20 Nov 2014, Russell King - ARM Linux wrote:
> > On Tue, Nov 18, 2014 at 04:49:21PM +, Stefano Stabellini wrote:
> > > ping?
> >
> > Sending something which wants my attention _To:_ me is always a good idea :)
>
> I
Signed-off-by: Wei Liu
Cc: Jan Beulich
---
tools/firmware/hvmloader/acpi/acpi2_0.h |8 +++
tools/firmware/hvmloader/acpi/build.c | 36 +++
2 files changed, 44 insertions(+)
diff --git a/tools/firmware/hvmloader/acpi/acpi2_0.h
b/tools/firmware/hvmloader/a
Libxc has more involvement in building vmemranges in HVM case. The
building of vmemranges is placed after xc_hvm_build returns, because it
relies on memory hole information provided by xc_hvm_build.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
Signed-off-by: Wei Liu
Cc: Jan Beulich
---
tools/firmware/hvmloader/acpi/acpi2_0.h | 53
tools/firmware/hvmloader/acpi/build.c | 68 +++
2 files changed, 121 insertions(+)
diff --git a/tools/firmware/hvmloader/acpi/acpi2_0.h
b/tools/fi
Changes:
1. Take care of function calls that can fail.
2. Use proper libxl error handling style.
3. Pass in build state instead of individual fields.
This is mechanical change in preparation for later patch.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_dom.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
index bace1cb..5980d87
Signed-off-by: Wei Liu
Cc: Jan Beulich
Cc: George Dunlap
---
tools/firmware/hvmloader/pci.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/tools/firmware/hvmloader/pci.c b/tools/firmware/hvmloader/pci.c
index 4e8d803..d7ea740 100644
--- a/tools/firmware/hvmloader/pci.c
+++
And then returns low memory end, high memory end and mmio start to
caller.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxc/include/xenguest.h |7 ++
tools/libxc/xc_hvm_build_x86.c | 224 ++
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_dom.c | 71 +++
1 file changed, 71 insertions(+)
diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
index 74ea84b..73
On 11/21/2014 10:14 AM, Konrad Rzeszutek Wilk wrote:
On Fri, Nov 21, 2014 at 11:08:37AM +0100, Juergen Gross wrote:
Hi,
during tests of my "linear p2m list" patches I stumbled over some
WARNs issued during xl save and xl restore of a pv-domU with
unpatched linux 3.18-rc5:
Boris had an patch fo
On Mon, Nov 17, 2014 at 10:29:19AM +, Ian Campbell wrote:
> On Mon, 2014-11-17 at 09:41 +, Wei Liu wrote:
> > On Mon, Nov 17, 2014 at 05:28:58PM +0800, Chao Peng wrote:
> > > Avoid sending duplicated qmp commands and eliminate the confusing error
> > > messages like "Unable to add CPU: 0, i
On 11/21/2014 03:54 PM, Jan Beulich wrote:
On 21.11.14 at 15:39, wrote:
Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
wrong device to the domain. The MMIO address was too large for a
MFN of a 32-bit system (it was 38000320-3800036f).
Instead of rejecting the operati
On Fri, Nov 21, 2014 at 11:08:37AM +0100, Juergen Gross wrote:
> Hi,
>
> during tests of my "linear p2m list" patches I stumbled over some
> WARNs issued during xl save and xl restore of a pv-domU with
> unpatched linux 3.18-rc5:
Boris had an patch for this I htink..
>
> during save I saw multip
On Fri, Nov 21, 2014 at 01:51:24PM +0100, Sander Eikelenboom wrote:
>
> Friday, November 21, 2014, 12:50:16 PM, you wrote:
>
> > On November 21, 2014 2:51:33 AM EST, Jan Beulich wrote:
> > On 20.11.14 at 20:51, wrote:
> >>> @@ -669,7 +670,7 @@ static void hvm_dirq_assist(struct domain *d,
>
On Fri, Nov 21, 2014 at 01:03:43PM +0100, Jan Beulich wrote:
> >>> On 21.11.14 at 12:50, wrote:
> > On November 21, 2014 2:51:33 AM EST, Jan Beulich wrote:
> > On 20.11.14 at 20:51, wrote:
> >>> @@ -669,7 +670,7 @@ static void hvm_dirq_assist(struct domain *d,
> >>struct hvm_pirq_dpci *pirq_
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxc/include/xc_dom.h |5 +++
tools/libxc/xc_dom_x86.c | 72 +++---
tools/libxc/xc_private.h |2 ++
3 files changed, 68 insertions(+)
Hi all
This patch series implements virtual NUMA support for both PV and HVM guest.
That is, admin can configure via libxl what virtual NUMA topology the guest
sees.
This is the stage 1 (basic vNUMA support) and part of stage 2 (vNUMA-ware
ballooning, hypervisor side) described in my previous ema
This vNUMA function (and future ones) is placed in a new file called
libxl_vnuma.c
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/Makefile |2 +-
tools/libxl/libxl_internal.h |5 ++
tools/libxl/libxl_vnuma.c|
Signed-off-by: Elena Ufimsteva
Signed-off-by: Wei Liu
Cc: Jan Beulich
---
xen/arch/x86/numa.c | 46 +-
1 file changed, 45 insertions(+), 1 deletion(-)
diff --git a/xen/arch/x86/numa.c b/xen/arch/x86/numa.c
index 628a40a..d27c30f 100644
--- a/xen/ar
One vmemrange is generated for each vnode. And for those guests who care
about machine E820 map, vmemranges are further split to accommodate
memory holes.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_arch.h |6 ++
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_types.idl |9 +
1 file changed, 9 insertions(+)
diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
index f7fc695..75855fb 100644
--- a/tools/li
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_arm.c |8
tools/libxl/libxl_x86.c |8
2 files changed, 16 insertions(+)
diff --git a/tools/libxl/libxl_arm.c b/tools/libxl/libxl_arm.c
index 448ac07.
Make XENMEM_increase_reservation and XENMEM_populate_physmap
vNUMA-aware.
That is, if guest requests Xen to allocate memory for specific vnode,
Xen can translate vnode to pnode using vNUMA information of that guest.
XENMEMF_vnode is introduced for the guest to mark the node number is in
fact virt
This function gets the machine E820 map and sanitize it according to PV
guest configuration.
This will be used in later patch.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_x86.c | 31 ++-
1
Currently we haven't exported vmemrange interface to libxl user.
Vmemranges are generated during domain build.
Signed-off-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Dario Faggioli
Cc: Elena Ufimtseva
---
tools/libxl/libxl_internal.h |3 +++
1 file changed, 3 insertions(+)
diff --g
1 - 100 of 172 matches
Mail list logo
