On Thu, Feb 09, 2017 at 12:42:09PM -0700, Tamas K Lengyel wrote:
> On Thu, Feb 9, 2017 at 11:39 AM, Julien Grall wrote:
> > Hi Tamas,
> >
> > On 02/09/2017 06:11 PM, Tamas K Lengyel wrote:
> >>
> >> On Wed, Feb 8, 2017 at 5:08 PM, Julien Grall wrote:
>
From: Ross Lagerwall
Date: Wed, 8 Feb 2017 10:57:37 +
> This fixes a crash when running out of grant refs when creating many
> queues across many netdevs.
>
> * If creating queues fails (i.e. there are no grant refs available),
> call xenbus_dev_fatal() to ensure
flight 105663 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105663/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 14 guest-saverestore fail REGR. vs. 59254
flight 105664 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105664/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 104585
Regressions
On Thu, Feb 9, 2017 at 11:43 AM, Stefano Stabellini
wrote:
> On Thu, 9 Feb 2017, Tamas K Lengyel wrote:
>> On Thu, Feb 9, 2017 at 11:22 AM, Stefano Stabellini
>> wrote:
>> > On Thu, 9 Feb 2017, Edgar E. Iglesias wrote:
>> >> On Thu, Feb 09, 2017 at
flight 105668 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105668/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
Den 2017-02-09 18:30, skrev Roger Pau Monné:
On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote:
I get the BUG below in dom0 when trying to start a windows 10 domu
(hvm,
with some pv-drivers installed ) . Below is "xl info", then comes
dmesg
output, and finally domu config
From: Vineeth Remanan Pillai
Date: Tue, 7 Feb 2017 18:59:01 +
> The commit 90c311b0eeea ("xen-netfront: Fix Rx stall during network
> stress and OOM") caused the refill timer to be triggerred almost on
> all invocations of xennet_alloc_rx_buffers for certain workloads.
>
On Thu, Feb 9, 2017 at 1:01 PM, Edgar E. Iglesias
wrote:
> On Thu, Feb 09, 2017 at 12:42:09PM -0700, Tamas K Lengyel wrote:
>> On Thu, Feb 9, 2017 at 11:39 AM, Julien Grall wrote:
>> > Hi Tamas,
>> >
>> > On 02/09/2017 06:11 PM, Tamas K Lengyel
On Thu, Feb 9, 2017 at 11:39 AM, Julien Grall wrote:
> Hi Tamas,
>
> On 02/09/2017 06:11 PM, Tamas K Lengyel wrote:
>>
>> On Wed, Feb 8, 2017 at 5:08 PM, Julien Grall wrote:
>>>
>>> On 08/02/2017 23:28, Tamas K Lengyel wrote:
On Wed, Feb 8,
flight 105655 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105655/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 14 guest-saverestore fail REGR. vs. 59254
On Thu, Feb 09, 2017 at 02:52:49AM -0700, Jan Beulich wrote:
> All,
>
> these stable releases are due in about 3 weeks time. Please indicate
> backports you consider necessary but find still missing. Commits
> already marked for backporting:
>
> e719192026 xen: credit2: never consider CPUs
On Thu, Feb 09, 2017 at 08:51:46AM +, Xuquan (Quan Xu) wrote:
>On February 08, 2017 4:22 PM, Chao Gao wrote:
>>On Wed, Feb 08, 2017 at 10:15:28AM +, Xuquan (Quan Xu) wrote:
>>>On February 08, 2017 4:52 PM, Jan Beulich wrote:
>>> On 08.02.17 at 09:27, wrote:
>
On 17-02-08 11:34:16, Konrad Rzeszutek Wilk wrote:
> > +/* No valid value so do not enable feature. */
> > +if ( !regs.a || !regs.b )
>
> You use regs.d below. Would it make sense to check for that value as
> well?
>
> Or is a value of 0 for cox_max OK? I would think so, but not exactly
On Thu, 2017-02-09 at 02:17 -0700, Jan Beulich wrote:
> > > > On 08.02.17 at 19:55, wrote:
> > I've only quickly tested it so far, and I have to leave now. I'll
> > play
> > with it a bit more tomorrow morning and let you know how it goes.
>
> Well, looking at the
libxl.c has grown to an uncomfortable size. Carve out the memory
related functions to libxl_mem.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile| 2 +-
tools/libxl/libxl.c | 577 --
tools/libxl/libxl_mem.c | 601
On Thu, Feb 09, 2017 at 10:30:14AM +0100, Juergen Gross wrote:
> The copyright of libxl.c is a little bit outdated.
>
> Adjust it to reality.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Wei Liu
___
Xen-devel
On Thu, 2017-02-09 at 02:17 -0700, Jan Beulich wrote:
> > > > On 08.02.17 at 19:55, wrote:
> I'm going to commit what I have later today, and
> I'll pull in the one extra backport next time round.
>
Ok, patch attached.
I've tested it on top of current tip of
>>> On 07.02.17 at 18:35, wrote:
> @@ -3178,9 +3179,9 @@ static enum hvm_copy_result __hvm_copy(
> {
> static unsigned long lastpage;
> if ( xchg(, gfn) != gfn )
> -gdprintk(XENLOG_DEBUG, "guest attempted
This run is configured for baseline tests only.
flight 68542 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68542/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 14
On Wed, Feb 08, 2017 at 04:15:59PM +0800, Yi Sun wrote:
> static void __init parse_psr_bool(char *s, char *value, char *feature,
> @@ -479,12 +495,14 @@ static struct psr_socket_info *get_socket_info(unsigned
> int socket)
> return socket_info + socket;
> }
>
> -int psr_get_info(unsigned
On Wed, Feb 08, 2017 at 04:15:55PM +0800, Yi Sun wrote:
> diff --git a/xen/arch/x86/psr.c b/xen/arch/x86/psr.c
> index 96a8589..4656936 100644
> --- a/xen/arch/x86/psr.c
> +++ b/xen/arch/x86/psr.c
> @@ -17,12 +17,118 @@
> #include
> #include
> #include
> +#include
Please move the inclusion
On Wed, Feb 08, 2017 at 10:05:38AM -0700, Jan Beulich wrote:
On 08.02.17 at 08:31, wrote:
>>> From: Jan Beulich [mailto:jbeul...@suse.com]
>>> Sent: Monday, February 06, 2017 11:38 PM
>>>
>>> >>> On 06.02.17 at 15:48, wrote:
>>> > On Mon,
>>> On 08.02.17 at 19:55, wrote:
> As per 4.7, I've prepared a branch for you:
Thanks.
> git://xenbits.xen.org/people/dariof/xen.git
> for-jan/staging-4.7/credit2-cpupool-fixes
>
> http://xenbits.xen.org/gitweb/?p=people/dariof/xen.git;a=shortlog;h=refs/head
>
libxl.c has grown to an uncomfortable size. Carve out the console
related functions (including channels, keyboard and frame buffer)
to libxl_console.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile| 2 +-
tools/libxl/libxl.c | 846
libxl.c has grown to an uncomfortable size. Carve out the disk
related functions to libxl_disk.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile |2 +-
tools/libxl/libxl.c | 1233 -
tools/libxl/libxl_disk.c | 1258
libxl.c has grown to an uncomfortable size. Carve out the domain
related functions to libxl_domain.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile |1 +
tools/libxl/libxl.c| 1722 ---
tools/libxl/libxl_domain.c
Splitting up libxl.c will require two functions to be globally visible.
Add their prototypes to libxl_internal.h.
Signed-off-by: Juergen Gross
---
tools/libxl/libxl.c | 12 ++--
tools/libxl/libxl_internal.h | 7 +++
2 files changed, 13 insertions(+), 6
The copyright of libxl.c is a little bit outdated.
Adjust it to reality.
Signed-off-by: Juergen Gross
---
tools/libxl/libxl.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
index d400fa2..0641a8a 100644
---
Before moving code to new sources clean up some white space issues in
libxl.c.
Signed-off-by: Juergen Gross
---
tools/libxl/libxl.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
index
libxl.c has grown to an uncomfortable size. Carve out the scheduler
related functions to libxl_sched.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl.c | 891
tools/libxl/libxl_sched.c |
Move the few generic device specific functions left in libxl.c to
libxl_device.c.
Signed-off-by: Juergen Gross
---
tools/libxl/libxl.c| 416 -
tools/libxl/libxl_device.c | 414
2
libxl.c has become rather large. Split it up into multiple files.
Changes are:
- modification of Copyright comment (patch 1)
- made two functions non-static: libxl__get_memory_target(),
xcinfo2xlinfo() (patch 2)
- white space cleanup of libxl.c (patch 3)
- moving functions into new or existing
libxl.c has grown to an uncomfortable size. Carve out the tmem
related functions to libxl_tmem.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl.c | 142
tools/libxl/libxl_tmem.c | 167
libxl.c has grown to an uncomfortable size. Carve out the cpupool
related functions to libxl_cpupool.c.
Signed-off-by: Juergen Gross
---
tools/libxl/Makefile| 1 +
tools/libxl/libxl.c | 418 -
tools/libxl/libxl_cpupool.c
On Thu, Feb 09, 2017 at 03:10:10AM -0700, Jan Beulich wrote:
> >>> On 07.02.17 at 18:35, wrote:
> > @@ -3178,9 +3179,9 @@ static enum hvm_copy_result __hvm_copy(
> > {
> > static unsigned long lastpage;
> > if ( xchg(, gfn) !=
Current code in acpi_os_map_memory uses the direct map in order to map memory
in the low 1MB, but acpi_os_unmap_memory doesn't takes that into account, and
always tries to perform a vunmap, which results in the following WARN:
(XEN) Xen WARN at vmap.c:185
(XEN) [ Xen-4.9-unstable x86_64
On Thu, 2017-02-09 at 10:00 +, osstest service owner wrote:
> flight 105655 linux-linus real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/105655/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>
>>> On 09.02.17 at 11:37, wrote:
> Current code in acpi_os_map_memory uses the direct map in order to map memory
> in the low 1MB, but acpi_os_unmap_memory doesn't takes that into account,
> and
> always tries to perform a vunmap, which results in the following WARN:
>
>
flight 105658 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105658/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 41ccec58e07376fe3086d3fb4cf6290c53ca2303
baseline version:
ovmf
On Thu, 2017-02-09 at 01:56 -0700, Jan Beulich wrote:
>
> > diff --git a/xen/arch/x86/hvm/mtrr.c b/xen/arch/x86/hvm/mtrr.c
> > index 86c71be..3d9386a 100644
> > --- a/xen/arch/x86/hvm/mtrr.c
> > +++ b/xen/arch/x86/hvm/mtrr.c
> > @@ -784,6 +784,8 @@ int epte_get_entry_emt(struct domain *d,
On February 08, 2017 4:22 PM, Chao Gao wrote:
>On Wed, Feb 08, 2017 at 10:15:28AM +, Xuquan (Quan Xu) wrote:
>>On February 08, 2017 4:52 PM, Jan Beulich wrote:
>> On 08.02.17 at 09:27, wrote:
Assumed vCPU is in guest_mode..
When apicv is enabled, hypervisor
All,
these stable releases are due in about 3 weeks time. Please indicate
backports you consider necessary but find still missing. Commits
already marked for backporting:
e719192026 xen: credit2: never consider CPUs outside of our cpupool.
(for 4.7.5 only, unless anyone cares to also provide 4.6
Hmm... not sure why my reply didn't have you in the To: field.
On Thu, Feb 09, 2017 at 10:13:13AM +, Wei Liu wrote:
> On Thu, Feb 09, 2017 at 10:47:01AM +0800, Haozhong Zhang wrote:
> > On 02/08/17 10:31 +, Wei Liu wrote:
> > > On Wed, Feb 08, 2017 at 02:07:26PM +0800, Haozhong Zhang
On 09/02/17 09:52, Jan Beulich wrote:
> All,
>
> these stable releases are due in about 3 weeks time. Please indicate
> backports you consider necessary but find still missing. Commits
> already marked for backporting:
>
> e719192026 xen: credit2: never consider CPUs outside of our cpupool.
> (for
On Wed, Feb 08, 2017 at 04:17:58PM +, George Dunlap wrote:
> On 08/02/17 16:11, Dario Faggioli wrote:
> > On Wed, 2017-02-08 at 14:51 +, George Dunlap wrote:
> >> Callers to libxl_cpupool_create() can either request a specific pool
> >> id, or request that Xen do it for them. But at the
On Wed, Feb 08, 2017 at 02:51:45PM +, George Dunlap wrote:
> Callers to xc_cpupool_create() can either request a specific pool id,
> or request that Xen do it for them. But at the moment, the
> "automatic" selection is indicated by using a magic value, 0. This is
> undesirable both because
On 02/08/2017 05:29 PM, Konrad Rzeszutek Wilk wrote:
. snip..
Reviewed-by: Konrad Rzeszutek Wilk
Couple of issues I found in sndif while preparing displif for review:
1. missing string constants
+#define XENSND_FIELD_BE_VERSIONS"versions"
+#define
>>> On 09.02.17 at 09:27, wrote:
> On Wed, Feb 08, 2017 at 10:05:38AM -0700, Jan Beulich wrote:
> On 08.02.17 at 08:31, wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Monday, February 06, 2017 11:38 PM
>>> On 06.02.17
On Wed, Feb 08, 2017 at 05:20:44PM -0800, Stefano Stabellini wrote:
> On Thu, 9 Feb 2017, Julien Grall wrote:
> > On 08/02/2017 23:28, Tamas K Lengyel wrote:
> > > On Wed, Feb 8, 2017 at 3:04 PM, Julien Grall wrote:
> > > > Hi Tamas,
> > > >
> > > > Can you please try to
On Thu, Feb 09, 2017 at 10:12:41AM +0100, Edgar E. Iglesias wrote:
> On Wed, Feb 08, 2017 at 05:20:44PM -0800, Stefano Stabellini wrote:
> > On Thu, 9 Feb 2017, Julien Grall wrote:
> > > On 08/02/2017 23:28, Tamas K Lengyel wrote:
> > > > On Wed, Feb 8, 2017 at 3:04 PM, Julien Grall
On Thu, Feb 09, 2017 at 09:51:48AM +0800, Zhang Chen wrote:
>
>
> On 02/09/2017 12:54 AM, Wei Liu wrote:
> > And CC Zhangchen
>
> Thanks, I will apply this patch set before test my patch.
>
This is not yet the final form. Please need to wait until this work gets
applied.
Wei.
flight 105660 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105660/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
On Thu, Feb 09, 2017 at 10:47:01AM +0800, Haozhong Zhang wrote:
> On 02/08/17 10:31 +, Wei Liu wrote:
> > On Wed, Feb 08, 2017 at 02:07:26PM +0800, Haozhong Zhang wrote:
> > > On 01/27/17 17:11 -0500, Konrad Rzeszutek Wilk wrote:
> > > > On Mon, Oct 10, 2016 at 08:32:34AM +0800, Haozhong Zhang
On Thu, Feb 09, 2017 at 10:30:13AM +0100, Juergen Gross wrote:
> libxl.c has become rather large. Split it up into multiple files.
>
> Changes are:
> - modification of Copyright comment (patch 1)
> - made two functions non-static: libxl__get_memory_target(),
> xcinfo2xlinfo() (patch 2)
> -
On Thu, Feb 09, 2017 at 01:56:14AM -0700, Jan Beulich wrote:
On 09.02.17 at 09:27, wrote:
>> On Wed, Feb 08, 2017 at 10:05:38AM -0700, Jan Beulich wrote:
>> On 08.02.17 at 08:31, wrote:
> From: Jan Beulich [mailto:jbeul...@suse.com]
>
On Thu, 2017-02-09 at 14:59 +0100, Dario Faggioli wrote:
> In fact, whether or not a pCPU has been tickled, and is
> therefore about to re-schedule, is something we look at
> and base decisions on in various places.
>
> So, let's make sure that we do that basing on accurate
> information.
>
>
On Wed, 8 Feb 2017, Konrad Rzeszutek Wilk wrote:
> > ## Ring Setup
> >
> > The shared page has the following layout:
> >
> > typedef uint32_t XEN_9PFS_RING_IDX;
> >
> > struct xen_9pfs_intf {
> > XEN_9PFS_RING_IDX in_cons, in_prod;
> > uint8_t pad[56];
> >
CC'ing Anthony
On Thu, 9 Feb 2017, Jan Beulich wrote:
> Stefano,
>
> the recent qemuu update results in the produced binary triggering the
> OOM killer on the first system I tried the updated code on. Is there
> anything known in this area? Are there any hints as to finding out
> what is going
On Fri, 3 Feb 2017, Edgar E. Iglesias wrote:
> On Thu, Feb 02, 2017 at 03:12:52PM -0800, Stefano Stabellini wrote:
> > On Thu, 2 Feb 2017, Edgar E. Iglesias wrote:
> > > On Wed, Feb 01, 2017 at 07:04:43PM +, Julien Grall wrote:
> > > > Hi Edgar,
> > > >
> > > > On 31/01/2017 19:06, Edgar E.
On Tue, 7 Feb 2017, Konrad Rzeszutek Wilk wrote:
> .snip..
> > Frontend XenBus Nodes
> >
> > version
> > Values:
> >
> > Protocol version, chosen among the ones supported by the backend
> > (see **versions** under [Backend XenBus Nodes]). Currently the
> > value
Hi all,
I have run some IRQ latency measurements on Xen on ARM on a Xilinx
ZynqMP board (four Cortex A53 cores, GICv2).
Dom0 has 1 vcpu pinned to cpu0, DomU has 1 vcpu pinned to cpu2.
Dom0 is Ubuntu. DomU is an ad-hoc baremetal app to measure interrupt
latency: https://github.com/edgarigl/tbm
I
flight 105674 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105674/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
On 02/09/17 10:13 +, Wei Liu wrote:
On Thu, Feb 09, 2017 at 10:47:01AM +0800, Haozhong Zhang wrote:
On 02/08/17 10:31 +, Wei Liu wrote:
> On Wed, Feb 08, 2017 at 02:07:26PM +0800, Haozhong Zhang wrote:
> > On 01/27/17 17:11 -0500, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Oct 10, 2016
flight 105669 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105669/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 15 guest-start/debian.repeat fail REGR. vs. 105629
Regressions which
flight 105672 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105672/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 14 guest-saverestore fail REGR. vs. 59254
test-amd64-i386-xl
flight 105675 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105675/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 18 leak-check/check fail REGR. vs. 104067
From: Oleksandr Andrushchenko
This is the ABI for the two halves of a para-virtualized
display driver.
This protocol aims to provide a unified protocol which fits more
sophisticated use-cases than a framebuffer device can handle. At the
moment basic
From: Oleksandr Andrushchenko
This is the ABI for the two halves of a para-virtualized
display driver.
This protocol aims to provide a unified protocol which fits more
sophisticated use-cases than a framebuffer device can handle. At the
moment basic
flight 105673 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105673/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 104585
Tests which
On 17-02-08 14:03:15, Konrad Rzeszutek Wilk wrote:
> > > +static void cpu_fini_work(unsigned int cpu)
> > > +{
> > > +unsigned int socket = cpu_to_socket(cpu);
> > > +
> > > +if ( !socket_cpumask[socket] ||
> > > cpumask_empty(socket_cpumask[socket]) )
> >
> > I fear I don't understand
On 09/02/17 10:35, Wei Liu wrote:
> On Wed, Feb 08, 2017 at 04:17:58PM +, George Dunlap wrote:
>> On 08/02/17 16:11, Dario Faggioli wrote:
>>> On Wed, 2017-02-08 at 14:51 +, George Dunlap wrote:
Callers to libxl_cpupool_create() can either request a specific pool
id, or request
On Thu, Feb 09, 2017 at 11:17:46AM +, George Dunlap wrote:
> On 09/02/17 10:35, Wei Liu wrote:
> > On Wed, Feb 08, 2017 at 04:17:58PM +, George Dunlap wrote:
> >> On 08/02/17 16:11, Dario Faggioli wrote:
> >>> On Wed, 2017-02-08 at 14:51 +, George Dunlap wrote:
> Callers to
The usage of the __transparent__ attribute in 991033fa introduces some issues
when compiled with clang 3.8.0:
xen/include/asm/hvm/vmx/vmx.h:605:15: error: transparent_union attribute can
only be
applied to a union definition; attribute ignored
[-Werror,-Wignored-attributes]
typedef union
Juergen Gross writes ("[PATCH v2 12/12] libxl: make one function static"):
> libxl__device_frontend_path() is used in libxl_device.c only. Make it
> static.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Juergen Gross writes ("[PATCH v2 00/12] libxl: split up libxl.c"):
> libxl: carve out cpupool specific functions from libxl.c
> libxl: carve out scheduler specific functions from libxl.c
> libxl: carve out disk specific functions from libxl.c
> libxl: carve out console specific functions
CC Roger and Konrad
On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote:
> I get the BUG below in dom0 when trying to start a windows 10 domu (hvm,
> with some pv-drivers installed ) . Below is "xl info", then comes dmesg
> output, and finally domu config attached at end.
>
> This
On 09/02/17 13:01, Jan Beulich wrote:
On 09.02.17 at 13:49, wrote:
>> On 09/02/17 11:33, Roger Pau Monne wrote:
>>> --- a/xen/include/asm-x86/hvm/vmx/vmx.h
>>> +++ b/xen/include/asm-x86/hvm/vmx/vmx.h
>>> @@ -602,15 +602,16 @@ void vmx_pi_hooks_assign(struct domain
The xenbus driver has an awful mixture of internally and globally
visible headers: some of the internally used only stuff is defined in
the global header include/xen/xenbus.h while some stuff defined in
internal headers is used by other drivers, too.
Clean this up by moving the externally used
Handling of multiple concurrent Xenstore accesses through xenbus driver
either from the kernel or user land is rather lame today: xenbus is
capable to have one access active only at one point of time.
Rewrite xenbus to handle multiple requests concurrently by making use
of the request id of the
Today a Xenstore watch event is delivered via a callback function
declared as:
void (*callback)(struct xenbus_watch *,
const char **vec, unsigned int len);
As all watch events only ever come with two parameters (path and token)
changing the prototype to:
void (*callback)(struct
The xenbus driver used for communication with Xenstore (all kernel
accesses to Xenstore and in case of Xenstore living in another domain
all accesses of the local domain to Xenstore) is rather simple
especially regarding multiple concurrent accesses: they are just being
serialized in spite of
On 02/09/2017 09:27 AM, Paul Durrant wrote:
-Original Message-
From: Paul Durrant [mailto:paul.durr...@citrix.com]
Sent: 09 February 2017 14:18
To: xen-de...@lists.xenproject.org; linux-ker...@vger.kernel.org
Cc: Paul Durrant ; Boris Ostrovsky
From: Vijaya Kumar K
Move common generic NUMA code to xen/common/numa.c from
xen/arch/x86/numa.c. Also move generic code in header file
xen/include/asm-x86/numa.h to xen/include/xen/numa.h
This common code can be re-used later for ARM.
Signed-off-by: Vijaya Kumar K
From: Vijaya Kumar K
With this RFC patch series, NUMA support is added for arm platform.
Both DT and ACPI based NUMA support is added.
Only Xen is made aware of NUMA platform. Dom0 is awareness is not
added.
As part of this series, the code under x86 architecture is
From: Vijaya Kumar K
Right not CONFIG_NUMA is not enabled for ARM and
existing code in asm-arm/numa.h is for !COFIG_NUMA.
Hence put this code under #ifndef CONFIG_NUMA.
This help to make this changes work when CONFIG_NUMA
is not enabled.
Also define NODES_SHIFT macro
From: Vijaya Kumar K
Move some common numa code from xen/arch/x86/srat.c
to xen/common/numa.c
Signed-off-by: Vijaya Kumar K
---
xen/arch/x86/srat.c| 54 -
xen/common/numa.c | 55
From: Vijaya Kumar K
When booting in UEFI mode, UEFI passes memory information
to Dom0 using EFI memory descriptor table and deletes the
memory nodes from the host DT. However to fetch the memory
numa node id, memory DT node should not be deleted by EFI stub.
With this
From: Vijaya Kumar K
numa_setup() contains generic and arch specific code.
Split numa_setup() and move architecture specific code
under arch_numa_setup().
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/Makefile | 1 +
xen/arch/arm/numa.c
From: Vijaya Kumar K
Register SRAT entry handler for type
ACPI_SRAT_TYPE_GICC_AFFINITY to parse SRAT table
and extract proximity for all CPU IDs.
Signed-off-by: Vijaya Kumar
---
xen/arch/arm/acpi_numa.c | 55
From: Vijaya Kumar K
Parse MADT table and extract MPIDR for all
CPU IDs in MADT ACPI_MADT_TYPE_GENERIC_INTERRUPT entries
and store in cpu_uid_to_hwid[].
This mapping is used by SRAT table parsing to
extract MPIDR of the CPU ID.
Signed-off-by: Vijaya Kumar
From: Vijaya Kumar K
Register SRAT entry handler for type
ACPI_SRAT_TYPE_MEMORY_AFFINITY to parse SRAT table
and extract proximity for all memory mappings.
Signed-off-by: Vijaya Kumar
---
xen/arch/arm/acpi_numa.c | 80
From: Vijaya Kumar K
Move srat_disabled() from xen/arch/x86/numa.c to
xen/commom/srat.c.
Signed-off-by: Vijaya Kumar
---
xen/arch/x86/numa.c| 7 ---
xen/common/srat.c | 7 +++
xen/include/asm-x86/acpi.h | 1 -
From: Vijaya Kumar K
On NUMA initialization failure, reset all the
NUMA structures to emulate as single node.
Signed-off-by: Vijaya Kumar
---
xen/arch/arm/numa.c | 50 --
1 file changed, 48
From: Vijaya Kumar K
Parse distance-matrix and fetch node distance information.
Store distance information in node_distance[].
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/dt_numa.c | 90 ++
From: Vijaya Kumar K
Delete numa-node-id and distance map from Dom0 DT
so that NUMA information is not exposed to Dom0.
This helps particularly to boot Node 1 devices
as if booting on Node0.
However this approach has limitation where memory allocation
for the devices
From: Vijaya Kumar K
Move SRAT handling code which is common across
architecture is moved to new file xen/commom/srat.c
from xen/arch/x86/srat.c file. New header file srat.h is
introduced.
Signed-off-by: Vijaya Kumar
---
From: Vijaya Kumar K
For each cpu, update cpu_to_node[] with node id from
the MPIDR registers. Also, initialize cpu_to_node[]
with node 0.
Add macros to access cpu_to_node[] information.
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/numa.c
From: Vijaya Kumar K
For all banks in bootinfo.mem, update nodes[] with
corresponding nodeid and register these nodes by
calling setup_node_bootmem().
compute memnode_shift and initialize memnodemap[] to fetch
nodeid for a given physical address.
Signed-off-by: Vijaya
From: Vijaya Kumar K
Parse CPU node and fetch numa-node-id information.
For each node-id found, update nodemask_t mask.
Call numa_init() from setup_mm() with start and end
pfn of the complete ram..
Signed-off-by: Vijaya Kumar K
---
1 - 100 of 188 matches
Mail list logo