flight 36524 seabios real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36524/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 7 windows-install fail REGR. vs. 35697
Tests which did not succe
branch xen-unstable
xen branch xen-unstable
job build-i386-rumpuserxen
test rumpuserxen-build
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: rumpuserxen https://github.com/rumpkernel/rumprun-xen
Tree: rumpus
On Thu, Mar 19, 2015 at 03:10:49PM +0200, Vitaly Chernooky wrote:
> David,
>
> On Thu, Mar 19, 2015 at 3:00 PM, David Vrabel
> wrote:
>
> > On 19/03/15 12:10, Iurii Konovalenko wrote:
> > > Hi, guys!
> > >
> > > When I read, that I am not alone and that issue depends on kernel
> > > version, I d
> -Original Message-
> From: Ian Campbell [mailto:ian.campb...@citrix.com]
> Sent: Thursday, March 19, 2015 8:57 PM
> To: Xu, Quan
> Cc: ke...@koconnor.net; stef...@linux.vnet.ibm.com; xen-devel@lists.xen.org;
> qemu-de...@nongnu.org; stefano.stabell...@eu.citrix.com
> Subject: Re: [Xen-d
On Thu, Mar 19, 2015 at 07:29:26PM +, Julien Grall wrote:
> Hello all,
>
> This is the fourth version of this patch series to add support for platform
> device passthrough on ARM.
>
> In order to passthrough a non-PCI device, the user will have to:
> - Map manually MMIO/IRQ
> - Descri
flight 36521 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36521/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 33488
test-amd64
On 2015/3/19 18:44, Ian Campbell wrote:
On Thu, 2015-03-19 at 10:07 +0800, Chen, Tiejun wrote:
This duplicates the code from above. I think this would be best done as:
static int libxl__detect_gfx_passthru_kind(libxl__gc *gc, guest_config)
{
if (b_info->u.hvm.gfx_passthru_kind != LIBXL_
> How about this (compile tested but not yet runtime tested):
Runtime tested now too.
I've put the whole lot (including this patch) on
git://xenbits.xen.org/people/konradwilk/xen.git xc_cleanup.v3
To ease pulling it in.
Thank you!
>
>
> From 92085d29b7e2906095a2bc6849b5a17b478e5c79 Mon Sep
Hello
I want to implement in xen hypervisor but I don't know how to do it. I
search in google but I do not found how to use the xen timer (not
linux).
when I compile xen the timer run only once. here is my code.
static void timer_handler(void *unused)
{
printk("hello world in timer\n")
flight 36526 xen-4.3-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36526/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 36483
build-amd64
On 03/19/2015 08:25 AM, Peter Zijlstra wrote:
On Thu, Mar 19, 2015 at 11:12:42AM +0100, Peter Zijlstra wrote:
So I was now thinking of hashing the lock pointer; let me go and quickly
put something together.
A little something like so; ideally we'd allocate the hashtable since
NR_CPUS is kinda b
Signed-off-by: Boris Ostrovsky
---
Changes in v5:
* Increment ti->first_dev in the loop
* Make node in xen_sysctl_pcitopoinfo a uint32
* Move sysctl to follow hearder file's order
* Update comments in sysctl.h
xen/common/sysctl.c | 61 +++
xen/
If ACPI provides PXM data for IO devices then dom0 will pass it to
hypervisor during PHYSDEVOP_pci_device_add call. This information,
however, is currently ignored.
We will store this information (in the form of nodeID) in pci_dev
structure so that we can provide it, for example, to the toolstack
Changes in v5:
* Make CPU topology and NUMA info sysctls behave more like
XEN_DOMCTL_get_vcpu_msrs
when passed NULL buffers. This required toolstack changes as well
* Don't use 8-bit data types in interfaces
* Fold interface version update into patch#3
Changes in v4:
* Split cputopology and NUM
SLIT values are byte-sized and some of them (0-9 and 255) have
special meaning. Adjust __node_distance() to reflect this and
modify scrub_heap_pages() and do_sysctl() to deal with
__node_distance() returning an invalid SLIT entry.
Signed-off-by: Boris Ostrovsky
---
Changes in v5:
* XEN_SYSCTL_nu
.. and use this new interface to display it along with CPU topology
and NUMA information when 'xl info -n' command is issued
The output will look like
...
cpu_topology :
cpu:coresocket node
0: 000
...
device topology:
device node
xc_cputopoinfo() is not expected to be used on a hot path and therefore
hypercall buffer management can be pushed into libxc. This will simplify
life for callers.
Also update error reporting macros.
Signed-off-by: Boris Ostrovsky
---
Changes in v5:
* Adjust to new interface (as described in chan
A number of changes to XEN_SYSCTL_topologyinfo interface:
* Instead of copying data for each field in xen_sysctl_topologyinfo separately
put cpu/socket/node into a single structure and do a single copy for each
processor.
* A NULL cputopo handle passed is a request for maximum number of CPUs
xc_numainfo() is not expected to be used on a hot path and therefore
hypercall buffer management can be pushed into libxc. This will simplify
life for callers.
Also update error logging macros.
Signed-off-by: Boris Ostrovsky
---
Changes in v5:
* Adjust to new interface (as described in changelog
A number of changes to XEN_SYSCTL_numainfo interface:
* Make sysctl NUMA topology query use fewer copies by combining some
fields into a single structure and copying distances for each node
in a single copy.
* NULL meminfo and distance handles are a request for maximum number
of nodes (num_n
On 03/19/2015 06:01 AM, Peter Zijlstra wrote:
On Wed, Mar 18, 2015 at 10:45:55PM -0400, Waiman Long wrote:
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
I do have some concern about this call site patching mechanism as the
modification is not atomic. The spin_unlock() calls are in many places in
On Thu, Mar 19, 2015 at 04:47:58PM +, Ian Campbell wrote:
> On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> > Instead of assuming everything is always OK. We stash
> > the gpfns value as an parameter.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk
> > ---
> > tools/libxc/xc_c
Hi,
On 19/03/15 19:29, Julien Grall wrote:
> The functions fdt_{fisrt,next}_subnode may not be available because:
> * It has been introduced in 2013 => Doesn't work on Wheezy
> * The prototype exists but the functions are not exposed. Don't ask
> why...
>
> The later has been fixed re
Let the user to pass additional nodes to the guest device tree. For
this purpose, everything in the node /passthrough from the partial
device tree will be copied into the guest device tree.
The node /aliases will be also copied to allow the user to define
aliases which can be used by the guest ker
On ARM, every non-PCI device are described in the device tree. Each of
them can be found via a path.
This patch introduces a very basic support, only the IOMMU will be set
up correctly. The user will have to:
- Describe the device in the partial device tree
- Map manually MMIO/IRQ
This is
ARM and x86 use a different hypercall to map an IRQ to a domain.
The hypercall to give IRQ permission to the domain as also been moved
on the x86 specific function as ARM guest won't be able to manage the IRQ.
We may want to support it later.
Signed-off-by: Julien Grall
Cc: Ian Jackson
Cc: Wei
The functions fdt_{fisrt,next}_subnode may not be available because:
* It has been introduced in 2013 => Doesn't work on Wheezy
* The prototype exists but the functions are not exposed. Don't ask
why...
The later has been fixed recently in the dtc repo [1]
When the functions are not a
Currently, when the device is deassigned from a domain, we directly reassign
to DOM0.
As the device may not have been correctly reset, this may lead to corruption or
expose some part of DOM0 memory. Also, we may have no way to reset some
platform devices.
If Xen reassigns the device to "nobody",
Each domain may have a different number of IRQs depending on the devices
assigned to it.
Rather re-using the number of IRQs used by the hardwared GIC, let the
toolstack specify the number of SPIs when the domain is created. This
will avoid to waste memory.
To calculate the number of SPIs, we take
On ARM the virtual GIC may differ between each guest (emulated GIC version,
number of SPIs...). This information is already known at the domain creation
and can never change.
For now only the gic_version is set. In the long run, there will be more
parameters such as the number of SPIs. All will be
The option "dtdev" will be used to passthrough a non-PCI device described
in the device tree to a guest.
Signed-off-by: Julien Grall
Cc: Ian Jackson
Cc: Wei Liu
---
Changes in v4:
- Typoes in the documentation
- Wrap the line in xl_cmdimpl.c
Changes in v2:
- li
This new function will correctly initialize the IOMMU page table for the
current domain.
Also use it in iommu_assign_dt_device even though the current IOMMU
implementation on ARM shares P2M with the processor.
Signed-off-by: Julien Grall
Cc: Jan Beulich
---
Changes in v4:
- Move me
Flask code already provides a helper to copy a string from guest. In a later
patch, the new DT hypercalls will need a similar function.
To avoid code duplication, copy the flask helper (flask_copying_string) to
common code:
- Rename into safe_copy_string_from_guest
- Add comment to explain
The structure pending_irq is initialized in the same way in 2 different
places. Introduce vgic_init_pending_irq to avoid code duplication.
Also move the setting of the irq field into this function as we need to
initialize it once rather than every time an IRQ is injected to the guest.
Finally, us
On x86, an IRQ is assigned in 2 steps to an HVM guest:
- The toolstack is calling PHYSDEVOP_map_pirq in order to create a
guest PIRQ (IRQ bound to an event channel)
- The emulator (QEMU) is calling DOMCTL_bind_pt_irq in order to
bind the IRQ
On ARM, there is no concept of PIRQ as t
The toolstack may not have deassigned every device used by a guest.
Therefore we have to go through the device list and remove them before
asking the IOMMU drivers to release memory for this domain.
This can be done by moving the call to the release function when we
relinquish the resources. The I
The maximum size of the copied string has been chosen based on the value
use by XSM in similar case.
Furthermore, Linux seems to allow path up to 4096 characters. Though
this could vary from one OS to another.
Signed-off-by: Julien Grall
---
Changes in v4:
- Drop DEVICE_TREE_MAX_PAT
The partial device tree may contains phandle. The Device Tree Compiler
tends to allocate the phandle from 1.
Reserve the ID 65000 for the GIC phandle. I think we can safely assume
that the partial device tree will never contain a such ID.
Signed-off-by: Julien Grall
Cc: Ian Jackson
Cc: Wei Liu
Note that the example is done on Midway whose SMMU driver is not
supported on Xen upstream.
Currently, I don't have other platform where I can test non-PCI
passthrough.
Signed-off-by: Julien Grall
---
Changes in v4:
- Patch added
---
docs/misc/arm/passthrough.txt | 58 +
A device node is described by a path. It will be used to retrieved the
node in the device tree and assign the related device to the domain.
Only non-PCI protected by an IOMMU can be assigned to a guest.
Also document the behavior of XEN_DOMCTL_deassign_device in the public
headers which differ be
With the addition of interrupt assignment to guest, we need to make sure
the guest can't blow up the interrupt management in Xen.
Before associating the IRQ to a vIRQ we need to make sure:
- the vIRQ is not already associated to another IRQ
- the guest didn't enable the vIRQ
Signed-off-by
This is a follow-up of commit 525ee49 "xsm: add device tree labeling
support" which add support for device tree labelling in flask.
Those helpers will be use latter when non-pci passthrough (i.e device
tree) will be added.
Signed-off-by: Julien Grall
Cc: Daniel De Graaf
---
Changes in v4:
Introduce spi_to_pending in order retrieve the irq_pending structure for
a specific SPI.
It's not possible to re-use irq_to_pending because it's required a VCPU
and some call of the new function may during domain destruction after
the VCPUs are freed.
Signed-off-by: Julien Grall
---
Changes
When a device is marked for passthrough (via the new property
"xen,passthrough"), dom0 must not access to the device (i.e not
loading a driver), but should be able to manage the MMIO/interrupt
of the passthrough device.
The latter part will allow the toolstack to map MMIO/IRQ when a device
is pass
The formula of GICD_TYPER.ITLinesNumber is 32(N + 1).
As the number of SPIs suppported by the domain may not be a multiple of
32, we have to round up the number before using it.
At the same time remove the mask GICD_TYPE_LINES which is pointless.
Signed-off-by: Julien Grall
---
Changes in
Currently Xen only supports SPIs routing for guest, add a function
is_assignable_irq to check if we can assign a given IRQ to the guest.
Secondly, make sure the vIRQ is not the greater that the number of IRQs
configured in the vGIC and it's an SPI.
Thirdly, when the IRQ is already assigned to the
Signed-off-by: Julien Grall
Acked-by: Stefano Stabellini
Acked-by: Ian Campbell
---
Changes in v4:
- Add Ian's ack
Changes in v3:
- Add Stefano's ack
Changes in v2:
- Don't move the call in common code.
---
xen/arch/arm/domctl.c | 11 ++-
1 file ch
The check to avoid mapping disabled devices in DOM0 was added in
anticipation of the device passthrough. But, a brand new property will
be added later to mark device which will be passthrough.
Also, remove the memory type check as we already skipped them earlier in
the function via skip_matches.
Xen has to release IRQ routed to a domain in order to reuse later.
Currently only SPIs can be routed to the guest so we only need to
browse SPIs for a specific domain.
Furthermore, a guest can crash and let the IRQ in an incorrect state
(i.e has not being EOIed). Xen will have to reset the IRQ in
Xen is only able to handle one GIC controller. Some platforms may contain
other interrupt controllers.
Make sure to only translate IRQ mapped into the GIC handled by Xen.
Signed-off-by: Julien Grall
Acked-by: Stefano Stabellini
Acked-by: Ian Campbell
---
Changes in v4:
- Add Ian'
The priority is already hardcoded in route_irq_to_guest and therefore
can't be controlled by the guest.
Signed-off-by: Julien Grall
---
Changes in v4:
- Patch added
---
xen/arch/arm/gic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/arm/gic.c b/xen/ar
GICD_TYPER.ITLinesNumber can encode up to 1024 interrupts. Although,
IRQ 1020-1023 are reserved for special purpose.
The result is used by the callers of gic_number_lines in order to check
the validity of an IRQ.
Signed-off-by: Julien Grall
Cc: Frediano Ziglio
Cc: Zoltan Kiss
---
The GIC
There is no reason to use signed integer for an index.
Signed-off-by: Julien Grall
Acked-by: Stefano Stabellini
Acked-by: Ian Campbell
---
Changes in v4:
- Add Ian's ack
Changes in v3:
- Slightly update commit message to drop the reference to new
hypercalls.
Suggested-by: Jan Beulich
Signed-off-by: Julien Grall
Cc: Ian Jackson
Cc: Keir Fraser
---
Changes in v4:
- Patch added
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d88fca3..3558164 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Currently, Xen is assuming that the virtual IRQ will always be the same
as IRQ.
Modify route_guest_irq to take the virtual IRQ in parameter which allow
Xen to assign a different IRQ number. Also store the vIRQ in the desc
action to easily retrieve the IRQ target when we need to inject the
interrup
Hello all,
This is the fourth version of this patch series to add support for platform
device passthrough on ARM.
In order to passthrough a non-PCI device, the user will have to:
- Map manually MMIO/IRQ
- Describe the device in the newly partial device tree support
- Specify the list
Currently the function to translate IRQ from the device tree is set
unconditionally to be able to be able to retrieve serial/timer IRQ before the
GIC has been initialized.
It assumes that the xlate function won't ever changed. We may also need to
have the primary interrupt controller very early.
>>> On 3/19/2015 at 12:09 PM, Anthony PERARD wrote:
> On Wed, Mar 18, 2015 at 04:12:26PM +, Ian Campbell wrote:
>> My second concern here is with the use of /var/run/xen/qmp-libxl-%i from
>> outside of libxl. I can't remember if qemu is safe against multiple
>> users of the socket. ISTR askin
On Thu, Mar 19, 2015 at 07:53:35AM +, Jan Beulich wrote:
> >>> On 17.03.15 at 16:38, wrote:
> > There is race when we clear the STATE_SCHED in the softirq
> > - which allows the 'raise_softirq_for' (on another CPU or
> > on the one running the softirq) to schedule the dpci.
> >
> > Specifical
On Thu, 2015-03-19 at 15:31 +0100, Juergen Gross wrote:
> --- a/arch/x86/xen/p2m.c
> +++ b/arch/x86/xen/p2m.c
> +#ifdef CONFIG_X86_32
> +BUILD_BUG_ON_MSG(CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT > 64)
> +#endif
I assume BUILD_BUG_ON_MSG() aborts the build.
> --- a/drivers/xen/Kconfig
> +++ b/dri
On Thu, Mar 19, 2015 at 03:03:55AM +, Wu, Feng wrote:
> Thanks for the comments!
>
> > -Original Message-
> > From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com]
> > Sent: Thursday, March 19, 2015 12:10 AM
> > To: Wu, Feng
> > Cc: xen-devel@lists.xen.org; Zhang, Yang Z; Tian, K
On Thu, Mar 19, 2015 at 04:39:49PM +, Ian Campbell wrote:
> On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> > The API returns now negative values on error and stashes
> > the error in errno. Fix the user of this API.
> >
> > The 'xc_hypercall_bounce_pre' can fail - and if so
On Thu, Mar 19, 2015 at 04:47:58PM +, Ian Campbell wrote:
> On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> > Instead of assuming everything is always OK. We stash
> > the gpfns value as an parameter.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk
> > ---
> > tools/libxc/xc_c
On Thu, Mar 19, 2015 at 06:22:06PM +0100, Juergen Gross wrote:
> On 03/19/2015 05:21 PM, Daniel Kiper wrote:
> >On Thu, Mar 19, 2015 at 03:31:02PM +0100, Juergen Gross wrote:
> >>Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
> >>regions above the end of RAM as 1:1") introduced a re
flight 36514 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36514/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-pair17 guest-migrate/src_host/dst_host fail like 35957
Tests which did not succeed,
On Thu, Mar 19, 2015 at 06:01:34PM +, David Vrabel wrote:
> This seems work for me, but I've not got time to give it a more thorough
> testing.
>
> You can fold this into your series.
Thanks!
> There doesn't seem to be a way to disable QUEUE_SPINLOCKS when supported by
> the arch, is this in
If multiple devices are being passed through to the same domain and they
share a single SMMU, then they only require a single iommu_domain.
In arm_smmu_assign_dev, before a new iommu_domain is created, the
xen_domain->contexts is checked for any iommu_domains that are already
assigned to device th
On Wed, Mar 18, 2015 at 04:12:26PM +, Ian Campbell wrote:
> My second concern here is with the use of /var/run/xen/qmp-libxl-%i from
> outside of libxl. I can't remember if qemu is safe against multiple
> users of the socket. ISTR asking Anthony this before, but I don't recall
> the answer, sor
flight 36520 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36520/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 10 migrate-support-checkfail never pass
test-amd64-i386-libvirt 10 migrate-sup
Hi all,
I have not seen anyone applying for Outreachy or working on any small projects
for Xen Project. But then I spot checked a number of mailing lists for other
orgs participating and it has not been that different for the other projects I
checked. It is possible that the name change is havin
On 16/03/15 13:16, Peter Zijlstra wrote:
>
> I feel that if someone were to do a Xen patch we can go ahead and merge this
> stuff (finally!).
This seems work for me, but I've not got time to give it a more thorough
testing.
You can fold this into your series.
There doesn't seem to be a way to d
flight 36512 xen-4.2-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36512/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-i386-i386-rumpuserxen-i386 1 build-check(1) blocked n/a
test-amd64-i386-rumpuserxen-i386 1 b
>>> On 3/18/2015 at 10:12 AM, Ian Campbell wrote:
> On Wed, 2015-03-11 at 11:51 -0600, Charles Arnold wrote:
>> Now that Xen uses qdisks by default and qemu does not write out
>> statistics to sysfs this patch queries the QMP for disk statistics.
>>
>> This patch depends on libyajl for parsing s
flight 36519 qemu-upstream-4.4-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36519/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 31663
Regress
On 19/03/15 17:19, Juergen Gross wrote:
> On 03/19/2015 05:18 PM, David Vrabel wrote:
>> On 19/03/15 14:31, Juergen Gross wrote:
>>> Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
>>> regions above the end of RAM as 1:1") introduced a regression.
>>>
>>> To be able to add memory pag
On 03/19/2015 05:21 PM, Daniel Kiper wrote:
On Thu, Mar 19, 2015 at 03:31:02PM +0100, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added via memory hot
On 19/03/15 17:16, Juergen Gross wrote:
> On 03/19/2015 05:18 PM, David Vrabel wrote:
>> On 19/03/15 14:31, Juergen Gross wrote:
>>> Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
>>> virtual mapped sparse p2m list") introduced a regression regarding to
>>> memory hotplug f
On 03/19/2015 05:18 PM, David Vrabel wrote:
On 19/03/15 14:31, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added via memory hotplug to
a pv domain, th
Several users have reported that their available free memory in the
guest when they used maxmem >> memory was much smaller than when
maxmem == memory. This is the unavoidable consequence of how
ballooning works, but it's not something users expect.
Warn them of this effect in the place we tell th
On Thu, 2015-03-19 at 13:18 +, Wei Liu wrote:
> This reverts commit dd748d128d86996592afafea02e578cc7d4e6d42.
>
> We don't need this workaround anymore since we have fixed the toolstack
> interlock problem that affects stubdom.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Campbell
But, really
On Thu, 2015-03-19 at 13:18 +, Wei Liu wrote:
> entries = libxl__xs_directory(gc, 0, GCSPRINTF(
> -"/local/domain/0/device-model/%d/physmap", domid), &num);
> +"/local/domain/%d/device-model/%d/physmap",
> +dm_domid, domid), &num);
You've mi
On 03/19/2015 05:18 PM, David Vrabel wrote:
On 19/03/15 14:31, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as the virtual space for the p2m list
On 03/19/2015 05:14 PM, Daniel Kiper wrote:
On Thu, Mar 19, 2015 at 03:31:01PM +0100, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as the virtual
On Thu, 2015-03-19 at 13:18 +, Wei Liu wrote:
> The function in question is libxl__spawn_local_dm. We should use
> LIBXL_TOOLSTACK_DOMID when constructing xenstore path.
>
> Currently LIBXL_TOOLSTACK_DOMID is 0, so this patch introduces no
> functional change.
>
> Use helper function to gener
On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> instead of the -Exx values (which should go in errno).
>
> This patch has HUGE implications. There is a lot of APIs
> that are using do_memory_op. Fortunately most of them
> check for 'if (do_memory_op(..) < 0)' so will function
> p
On Thu, 2015-03-19 at 13:18 +, Wei Liu wrote:
> ... and not devices_destroy_cb because it is the right place to clean up
> device model stuff.
>
> And the path should use LIBXL_TOOLSTACK_DOMID instead of hardcoded 0.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Campbell
On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> Instead of assuming everything is always OK. As such
> we return now the return value (or zero for success).
> The max_mfn is now passed in as the parameter.
>
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
On Thu, 2015-03-19 at 13:18 +, Wei Liu wrote:
> Introduce this helper to return xenstore path for device model to avoid
> handcoded paths.
>
> Signed-off-by: Wei Liu
> ---
> tools/libxl/libxl_internal.c | 22 ++
> tools/libxl/libxl_internal.h | 3 +++
> 2 files changed,
On 03/19/2015 04:53 PM, Boris Ostrovsky wrote:
On 03/19/2015 10:31 AM, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as the virtual space for the p
On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> If there is a negative return value - check for that and
> also use errno for the proper error value.
>
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
___
Xen-devel ma
On Thu, 19 Mar 2015 16:35:43 +, Ian Campbell wrote:
On Thu, 2015-03-19 at 17:04 +0100, HANNAS YAYA Issa wrote:
Please ask user configuration questions on the xen-users list, this
list
is for development topics.
Perhaps also check your favourite search engine before doing so.
Ian.
Hi
wh
On 19/03/15 03:40, openlui wrote:
Hi, all:
I am trying to use a HVM with PCI pass-through NIC as network driver domain.
However, when I send packets whose size are larger than 128 bytes from DomU
using pkt-gen tools, after several seconds, the network between driver domain
and destination h
On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> Instead of assuming everything is always OK. We stash
> the gpfns value as an parameter.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> tools/libxc/xc_core_arm.c| 17 ++---
> tools/libxc/xc_core_x86.c| 24 +++
On Tue, 2015-03-17 at 14:16 -0400, longtao.pang wrote:
> From: "longtao.pang"
>
> 1. Designate vif model to 'e1000', otherwise, with default device model,
> the L1 eth0 interface disappear, hence xenbridge cannot work.
> Maybe this limitation can be removed later after some fix it. For now, we
>
On Wed, 2015-03-18 at 20:24 -0400, Konrad Rzeszutek Wilk wrote:
> The API returns now negative values on error and stashes
> the error in errno. Fix the user of this API.
>
> The 'xc_hypercall_bounce_pre' can fail - and if so it will
> stash its errno values - no need to over-write it.
>
> Signed
On Thu, 2015-03-19 at 17:04 +0100, HANNAS YAYA Issa wrote:
Please ask user configuration questions on the xen-users list, this list
is for development topics.
Perhaps also check your favourite search engine before doing so.
Ian.
> Hi
> when I run xen-access test (tools/tests/xen-access) I got t
On Tue, 2015-03-17 at 14:16 -0400, longtao.pang wrote:
> This patch set adds nested HVM test case for osstest.
I've now looked at the first two patches in this series and I've found
that in both patches you have consistently not reacted to the review
comments made the first time around, so I'm not
On Thu, Mar 19, 2015 at 03:31:02PM +0100, Juergen Gross wrote:
> Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
> regions above the end of RAM as 1:1") introduced a regression.
>
> To be able to add memory pages which were added via memory hotplug to
> a pv domain, the pages must be
On 19/03/15 14:31, Juergen Gross wrote:
> Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
> regions above the end of RAM as 1:1") introduced a regression.
>
> To be able to add memory pages which were added via memory hotplug to
> a pv domain, the pages must be "invalid" instead of
On 19/03/15 14:31, Juergen Gross wrote:
> Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
> virtual mapped sparse p2m list") introduced a regression regarding to
> memory hotplug for a pv-domain: as the virtual space for the p2m list
> is allocated for the to be expected mem
1 - 100 of 226 matches
Mail list logo
