Do we have any requirements to be compatible to old releases regarding
the functions in tools/python/xen/lowlevel/xc/xc.c ?
Especially pyxc_linux_build() isn't used anywhere in the tree. And this
is the only function setting xc_dom_image.superpages, thus removing it
would give us the chance to re
flight 62659 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62659/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 11 guest-start fail REGR. vs. 62318
test-amd64-i386-xl-qemu
Hi Steven
On Tue, Oct 06, 2015 at 03:50:10PM +1100, Steven Haigh wrote:
> On 2015-10-06 15:29, Andy Smith wrote:
> >- Your typical EntropyKey or OneRNG can generate quite a bit of
> > entropy. Maybe 32 kilobytes per second for ~$50 each.
>
> If you can get one... :)
Yeah, EntropyKeys aren't rea
On 2015-10-06 15:29, Andy Smith wrote:
- Your typical EntropyKey or OneRNG can generate quite a bit of
entropy. Maybe 32 kilobytes per second for ~$50 each.
If you can get one... :)
- You can access them over the network so no USB passthrough needed.
Care to give details on this? I've got
On 10/05/2015 09:29 PM, Andy Smith wrote:
> I don't find it a problem as:
>
> - Your typical EntropyKey or OneRNG can generate quite a bit of
> entropy. Maybe 32 kilobytes per second for ~$50 each.
>
> - You can access them over the network so no USB passthrough needed.
Yes, I'm implementing
Hi Sarah,
On Mon, Oct 05, 2015 at 09:12:47PM -0700, Sarah Newman wrote:
> On 10/05/2015 08:35 PM, Andy Smith wrote:
> > So, I've been keeping (PV) domUs topped up with entropy by giving
> > them access to hardware RNGs (initially Entropy Keys, but since the
> > company making them failed I've swit
flight 62651 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62651/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 12 guest-start/redhat.repeat fail REGR. vs.
58581
Regressions whi
On 10/05/2015 08:35 PM, Andy Smith wrote:
> So, I've been keeping (PV) domUs topped up with entropy by giving
> them access to hardware RNGs (initially Entropy Keys, but since the
> company making them failed I've switched to OneRNGs).
This is not a satisfactory solution for us because even if we
This run is configured for baseline tests only.
flight 38126 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38126/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pygrub 20 guest-start/deb
Hi,
On Mon, Oct 05, 2015 at 06:33:49PM -0700, Sarah Newman wrote:
> We would like to use something like virtio-rng
> http://wiki.qemu-project.org/Features-Done/VirtIORNG with PVM domUs and since
> the wiki page on virtio
> http://wiki.xen.org/wiki/Virtio_On_Xen says the wiki page is out of date,
Greetings,
We would like to use something like virtio-rng
http://wiki.qemu-project.org/Features-Done/VirtIORNG with PVM domUs and since
the wiki page on virtio
http://wiki.xen.org/wiki/Virtio_On_Xen says the wiki page is out of date, what
is the current status?
Would a native xen driver be lik
flight 62649 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62649/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 11 guest-start fail REGR. vs. 62339
Tests which did not succeed,
On 10/5/15 5:03 PM, Doug Goldstein wrote:
> This is very incomplete and is only posted in hopes of getting some feedback
> if this conversion is welcome by the community. There are a few different
> ways I can go from here.
>
> * convert all of include/$(ARCH)/config.h
> * move this to the top lev
On 05/10/15 11:16, Konrad Rzeszutek Wilk wrote:
It looks to be missing in the policy file for the initial
domain. Eventually we may want to extend this access to
non-dom0 domains but for now it certainly dom0-only.
Reviewed-by: Boris Ostrovsky
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: D
> On 5 Oct 2015, at 15:32, Jan Beulich wrote:
>
>> ! We do appear to have some issues in this area, which will need to be
>> explored
>> ! further. In particular because the earlier questions Q1.1 - Q1.4 imply
>> ! that some sort of hierarchy based on seniority is not seen as a problem by
>> !
Hi,
On 05/10/2015 23:03, Doug Goldstein wrote:
Use the Kconfig generated CONFIG_HAS_GICV3 defines in the code base.
If you are going to rename all HAS_* to CONFIG_HAS_, please drop the HAS
which is now redundant.
Signed-off-by: Doug Goldstein
---
xen/arch/arm/Kconfig | 4
Hi,
Can you please run scripts/get_maintainers.pl on every patch to get the
list of relevant maintainers.
Regards,
On 05/10/2015 23:03, Doug Goldstein wrote:
This is very incomplete and is only posted in hopes of getting some feedback
if this conversion is welcome by the community. There are
Use the Kconfig generated CONFIG_HAS_MEM_SHARING defines in the code base.
Signed-off-by: Doug Goldstein
---
config/x86_32.mk| 1 -
config/x86_64.mk| 1 -
xen/Rules.mk| 1 -
xen/arch/x86/Kconfig| 1 +
xen/common/Kconfig | 4
xen/common/memory.c | 2 +
Signed-off-by: Doug Goldstein
---
config/x86_64.mk | 1 -
xen/arch/x86/Kconfig | 8
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/config/x86_64.mk b/config/x86_64.mk
index 7899fd5..fcae0b1 100644
--- a/config/x86_64.mk
+++ b/config/x86_64.mk
@@ -2,7 +2,6 @@ CONFIG_X86
Use the Kconfig generated CONFIG_HAS_GICV3 defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/arm/Kconfig | 4
xen/arch/arm/Makefile| 2 +-
xen/arch/arm/Rules.mk| 2 --
xen/arch/arm/vgic.c | 2 +-
xen/include/asm-arm/domain.h | 3 ++-
xen/i
Use the Kconfig generated CONFIG_HAS_MEM_ACCESS defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/arm/Kconfig | 1 +
xen/arch/x86/Kconfig | 1 +
xen/common/Kconfig | 4
xen/common/Makefile | 2 +-
xen/
Use the Kconfig generated CONFIG_HAS_EHCI defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
4 files changed, 6 insertions(+), 2 deletions(-)
diff --g
Use the Kconfig generated CONFIG_HAS_VGA defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/video/Makefile | 4 ++--
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/xen/arch/x86/Kconfig b/xen/
Use the Kconfig generated CONFIG_HAS_ARM_HDLCD defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/arm/Kconfig | 1 +
xen/arch/arm/Rules.mk | 2 --
xen/drivers/video/Makefile | 2 +-
3 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/Kconfig b
Use the Kconfig generated CONFIG_HAS_EXYNOS4210 defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
inde
Use the Kconfig generated CONFIG_HAS_IOPORTS defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/char/Kconfig | 5 +
xen/drivers/char/ns16550.c | 10 +-
5 f
Use the Kconfig generated CONFIG_HAS_CPUFREQ defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/x86/Kconfig| 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/Kconfig | 2 ++
xen/drivers/Makefile| 2 +-
xen/drivers/cpufreq/Kconfig | 4
5 files cha
Wire in the Kconfig build and makefile rules to be able to generate
valid configuration files to be used by the build process.
Signed-off-by: Doug Goldstein
---
.gitignore| 8
xen/Kconfig | 26 ++
xen/Makefile
Use the Kconfig generated CONFIG_HAS_MEM_PAGING defines in the code base.
Signed-off-by: Doug Goldstein
---
config/x86_32.mk| 1 -
config/x86_64.mk| 1 -
xen/Rules.mk| 1 -
xen/arch/x86/Kconfig| 1 +
xen/common/Kconfig | 4
xen/common/memory.c | 2 +-
Use the Kconfig generated CONFIG_HAS_SCIF defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
index f06e
This is very incomplete and is only posted in hopes of getting some feedback
if this conversion is welcome by the community. There are a few different
ways I can go from here.
* convert all of include/$(ARCH)/config.h
* move this to the top level and convert all of configs/
* due both of the above
Use the Kconfig generated CONFIG_HAS_GDBSX defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/x86/Rules.mk | 1 -
xen/common/Kconfig| 4
xen/common/domain.c | 2 +-
4 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/xen/Rules.
Use the Kconfig generated CONFIG_HAS_KEXEC defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 2 +-
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/common/Kconfig| 4
4 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/xen/Rules.
Replace kexec := y in Rules.mk with a Kconfig option called CONFIG_KEXEC
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 6 --
xen/common/Kconfig | 11 +++
2 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/xen/Rules.mk b/xen/Rules.mk
index 0742b06..9480ad0 10064
Use the Kconfig generated CONFIG_HAS_VIDEO defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/arm/Kconfig | 1 +
xen/arch/arm/Rules.mk | 1 -
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/Kconfig| 2 ++
xen/drivers/Makef
Use the Kconfig generated CONFIG_HAS_PCI defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk| 1 -
xen/common/sysctl.c | 2 +-
xen/drivers/Kconfig
Use the Kconfig generated CONFIG_HAS_NS16550 defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/drivers/Kconfig | 2 ++
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
5 files changed, 8 in
Use the Kconfig generated CONFIG_HAS_DEVICE_TREE defines in the code
base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/arm/Kconfig | 1 +
xen/arch/arm/Rules.mk| 1 -
xen/common/Kconfig | 4
xen/common/Makefile
Use the Kconfig generated CONFIG_HAS_PL011 defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
index a79
Use the Kconfig generated CONFIG_HAS_PDX defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/arm/Kconfig | 1 +
xen/arch/arm/Rules.mk | 1 -
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk | 1 -
xen/common/Kconfig| 4
xen/common/Makefil
Use the Kconfig generated CONFIG_HAS_OMAP defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
index 9124
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 2 ++
xen/include/xen/config.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/xen/Rules.mk b/xen/Rules.mk
index bf19d20..01ec6d2 100644
--- a/xen/Rules.mk
+++ b/xen/Rules.mk
@@ -12,6 +12,8 @@ frame_pointer ?= n
lto ?=
Use the Kconfig generated CONFIG_HAS_ACPI defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk | 1 -
xen/arch/x86/Kconfig | 1 +
xen/arch/x86/Rules.mk| 1 -
xen/common/sysctl.c | 2 +-
xen/drivers/Kconfig | 2 ++
xen/drivers/Makefile | 2 +-
Use the Kconfig generated CONFIG_HAS_CADENCE_UART defines in the code base.
Signed-off-by: Doug Goldstein
---
xen/drivers/char/Kconfig | 4
xen/drivers/char/Makefile | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
in
Signed-off-by: Doug Goldstein
---
xen/scripts/basic/.gitignore | 1 -
xen/scripts/basic/Makefile | 1 -
2 files changed, 2 deletions(-)
diff --git a/xen/scripts/basic/.gitignore b/xen/scripts/basic/.gitignore
index 9528ec9..a776371 100644
--- a/xen/scripts/basic/.gitignore
+++ b/xen/scripts/ba
Use the Kconfig generated HAS_PASSTHROUGH defines for the code base.
Signed-off-by: Doug Goldstein
---
xen/Rules.mk| 1 -
xen/arch/arm/Kconfig| 1 +
xen/arch/arm/Rules.mk | 1 -
xen/arch/x86/Kconfig| 1 +
xen/arch/x86/Rules.mk |
Hi everyone,
questions related to the items below are welcome; in particular if anyone
suspects the data is wrong. Some if the data is still incomplete, or only
covers 2015. Once I have more, I will share.
[1]
https://github.com/dicortazar/ipython-notebooks/blob/master/projects/xen-analysis/Co
This run is configured for baseline tests only.
flight 38124 linux-3.10 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38124/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-
flight 62648 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62648/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-rumpuserxen-i386 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 60666
test-a
This run is configured for baseline tests only.
flight 38125 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38125/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 63e1c23b225578efdaca714a81055eadb0a07cec
baseline version:
ovm
CONFIG_HVM is not used anywhere in the build process so drop it.
Signed-off-by: Doug Goldstein
---
config/x86_32.mk | 1 -
config/x86_64.mk | 1 -
2 files changed, 2 deletions(-)
diff --git a/config/x86_32.mk b/config/x86_32.mk
index c2d785e..ed69447 100644
--- a/config/x86_32.mk
+++ b/config/x
flight 62680 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62680/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
flight 62646 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62646/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-qcow2 6 xen-bootfail REGR. vs. 62583
test-amd64-i386-xl-qemut-stub
Hi,
On 05/10/15 17:38, Brijesh Singh wrote:
> As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
> call function ID parameter should be set to SMC64 version.
>
> Signed-off-by: Brijesh Singh
Reviewed-by: Julien grall
Regards,
--
Julien Grall
On 05/10/15 17:01, Roger Pau Monné wrote:
> El 11/09/15 a les 21.32, Julien Grall ha escrit:
>> The minimal size of request in the block framework is always PAGE_SIZE.
>> It means that when 64KB guest is support, the request will at least be
>> 64KB.
>>
>> Although, if the backend doesn't support i
El 05/10/15 a les 12.36, Andrew Cooper ha escrit:
> On 02/10/15 16:49, Roger Pau Monne wrote:
>> This structure contains the physical address of the command line, as well as
>> the physical address of the list of loaded modules. The physical address of
>> this structure is passed to the guest at bo
>
> > @@ -1467,6 +1503,56 @@ int
> mem_sharing_memop(XEN_GUEST_HANDLE_PARAM(xen_mem_sharing_op_t) arg)
> > }
> > break;
> >
> > +case XENMEM_sharing_op_bulk_dedup:
> > +{
> > +unsigned long max_sgfn, max_cgfn;
> > +struct domain *cd;
> > +
>
El 02/10/15 a les 20.37, Andrew Cooper ha escrit:
> On 02/10/15 16:48, Roger Pau Monne wrote:
>> If certain devices (like the local or the io apic) are disabled some modes
>> of operation of the HVM event channel callback cannot be used. Make sure Xen
>> doesn't try to setup them.
>>
>> Signed-off-
On 05/10/15 17:40, Roger Pau Monné wrote:
> El 05/10/15 a les 11.34, Andrew Cooper ha escrit:
>> On 02/10/15 16:48, Roger Pau Monne wrote:
>>> Introduce a bitmap in x86 xen_arch_domainconfig that allows enabling or
>>> disabling specific devices emulated inside of Xen for HVM guests.
>>>
>>> Signed
On Mon, Oct 05, 2015 at 05:34:11PM +0100, Ian Jackson wrote:
> Dario Faggioli writes ("[OSSTEST PATCH 2/2] make-flight: create the vNUMA HVM
> test job"):
> > as a variant of regular Debian HVM jobs.
> >
> > For now, the vNUMA topology is just hardcoded
> > here, and it is 4 vCPUs and 2 vNUMA nod
Mike Latimer writes ("[PATCH v3 1/1] tools/hotplug: Scan xenstore once when
attaching shared images files"):
> During the attachment of a loopback mounted image file, the mode of all
> curent instances of this device already attached to other domains must be
> checked. This requires finding all lo
Ian Campbell writes ("Re: [PATCH OSSTEST] Switch to merged
qemu-xen{,-traditional}.git trees"):
> Yes, v2 is below for completeness. I rebased this over the smoketest stuff
> which added $xenbranch_forqemu which of course is now no longer needed so
> the rebase just involved taking my version of e
El 05/10/15 a les 11.34, Andrew Cooper ha escrit:
> On 02/10/15 16:48, Roger Pau Monne wrote:
>> Introduce a bitmap in x86 xen_arch_domainconfig that allows enabling or
>> disabling specific devices emulated inside of Xen for HVM guests.
>>
>> Signed-off-by: Roger Pau Monné
>> Acked-by: Wei Liu
>
As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
call function ID parameter should be set to SMC64 version.
Signed-off-by: Brijesh Singh
---
xen/arch/arm/psci.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/psci.c b/xen/arch
Mike Latimer writes ("[PATCH v2 1/1] tools/hotplug: Scan xenstore once when
attaching shared images files"):
> During the attachment of a loopback mounted image file, the mode of all
> curent instances of this device already attached to other domains must be
> checked. This requires finding all lo
Dario Faggioli writes ("[OSSTEST PATCH 2/2] make-flight: create the vNUMA HVM
test job"):
> as a variant of regular Debian HVM jobs.
>
> For now, the vNUMA topology is just hardcoded
> here, and it is 4 vCPUs and 2 vNUMA nodes. How
> to split resources is left to the test
> implementation (right
On 10/05/2015 11:03 AM, Julien Grall wrote:
> Hi,
>
> From the commit title, it's not clear that you are touching the PSCI code.
>
> I would rewrite it like:
>
> "xen/arm: psci: use SMC64 function ID when available on ARM64"
>
> On 05/10/15 16:27, Brijesh Singh wrote:
>> As per PSCI 0.2 spec,
Ian Campbell writes ("Re: [Xen-devel] [PATCH OSSTEST 4/6] ts-freebsd-install:
Use $gho->{Lvdev} instead of target_guest_lv_name"):
> On Thu, 2015-10-01 at 11:45 +0100, Ian Campbell wrote:
> > I'm in two minds about having guest_find_lv use lv_dev_mapper to populate
> > $gho->{Lvdev} in the first p
Ian Campbell writes ("[PATCH OSSTEST 8/8] Debian: Use dtbs from kernel dist
when booting that kernel"):
> The kernel dist built by ts-kernel-build puts the corresponding dtbs
> into /boot/dtbs/$kvers.
>
> The host installers dtbs remain in /boot/dtbs and are used when
^
Missin
On Mon, 2015-10-05 at 17:24 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 7/8] Debian: Enable interpolation in
> uboot_scr_load_dtb here doc"):
> > By switching <<'END' to < > a variable here which requires interpretation by the Perl.
> >
> > Unfortunately this means lots of ext
On Mon, 2015-10-05 at 17:22 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 6/8] ts-kernel-build: Include dtbs
> in dist file"):
> > These are installed to $(INSTALL_PATH)/dtbs/$(KERNEL_RELEASE) where
> > $(INSTALL_PATH) defaults to /boot but we override it to our staging
> > /boot
On Mon, 2015-10-05 at 17:20 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 5/8] ts-kernel-build: Add arm64
> support"):
> > And to Osstest::%arch_debian2*.
> >
> > Untested (but hopefully pretty obvious).
>
> Acked-by: Ian Jackson
>
> > my $archparms = {
> > +'arm64' => {
Ian Campbell writes ("[PATCH OSSTEST 7/8] Debian: Enable interpolation in
uboot_scr_load_dtb here doc"):
> By switching <<'END' to < a variable here which requires interpretation by the Perl.
>
> Unfortunately this means lots of extra backticks to escape things such
> that they pass through Perl
Ian Campbell writes ("[PATCH OSSTEST 1/8] Osstest: Add %arch_debian2linux (and
inverse)"):
> Modelled after %arch_debian2xen.
>
> Will be used in ts-kernel-build.
Acked-by: Ian Jackson
> +our %arch_linux2debian;
> +$arch_linux2debian{$arch_debian2linux{$_}} = $_ foreach keys %arch_debia\
n2lin
Ian Campbell writes ("[PATCH OSSTEST 6/8] ts-kernel-build: Include dtbs in dist
file"):
> These are installed to $(INSTALL_PATH)/dtbs/$(KERNEL_RELEASE) where
> $(INSTALL_PATH) defaults to /boot but we override it to our staging
> /boot.
Thanks for the detailed explanation.
Acked-by: Ian Jackson
On Tue, Oct 06, 2015 at 12:21:18AM +1100, Steven Haigh wrote:
> On 6/10/2015 12:05 AM, George Dunlap wrote:
> > On Mon, Oct 5, 2015 at 12:44 PM, Steven Haigh wrote:
> >> On 5/10/2015 10:23 PM, Wei Liu wrote:
> >>> On Mon, Oct 05, 2015 at 05:04:19AM -0600, Jan Beulich wrote:
> >>> On 02.10.15 a
On Mon, 2015-10-05 at 16:53 +0100, Stefano Stabellini wrote:
> > Wasn't there some code to plumb this into xl at one point? Did that get
> > dropped along the way?
>
> device_model_user is added to the idl by this patch, I think that is
> enough, right?
Depends what you mean by "enough", it adds
Ian Campbell writes ("[PATCH OSSTEST 5/8] ts-kernel-build: Add arm64 support"):
> And to Osstest::%arch_debian2*.
>
> Untested (but hopefully pretty obvious).
Acked-by: Ian Jackson
> my $archparms = {
> +'arm64' => { Image => 'Image' },
IWBN to double-check that t
Ian Campbell writes ("[PATCH OSSTEST 4/8] ts-kernel-build: Refactor $archparams
KernelImage handling"):
> This is always arch/$karch/boot/$img. Store $img in %archparms and use
> %arch_debian2linux to construct the full path as needed.
>
> This makes the $archparams less verbose.
Acked-by: Ian J
Ian Campbell writes ("[PATCH OSSTEST 3/8] ts-kernel-build: Refactor
$archparams::DefConfig selection"):
> This is always either "foo_defconfig" or "defconfig". Record only
> "foo" or undef and construct the name.
Acked-by: Ian Jackson
___
Xen-devel ma
On Fri, 2015-10-02 at 09:25 -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Oct 02, 2015 at 10:51:34AM +0100, Ian Campbell wrote:
> > (trimming and reordering To/Cc)
> >
> > On Thu, 2015-10-01 at 16:15 +0100, David Vrabel wrote:
> > > On 30/09/15 11:45, Julien Grall wrote:
> > > > Hi all,
> > > >
>
El 05/10/15 a les 12.05, Jan Beulich ha escrit:
On 02.10.15 at 17:48, wrote:
>> --- a/xen/common/compat/domain.c
>> +++ b/xen/common/compat/domain.c
>> @@ -23,6 +23,8 @@ CHECK_SIZE_(struct, vcpu_info);
>> CHECK_vcpu_register_vcpu_info;
>> #undef xen_vcpu_register_vcpu_info
>>
>> +extern v
Ian Campbell writes ("[PATCH OSSTEST 2/8] ts-kernel-build: Introduce global
$parms"):
> Which contains the relevant details from %archparms, making the use
> sites simpler.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http:/
This check is missing from the compat version when compared to the
non-compat version.
Signed-off-by: Roger Pau Monné
Cc: Ian Campbell
Cc: Jan Beulich
Cc: Tim Deegan
Cc: Andrew Cooper
---
Changes since v1:
- Moved the declaration of dummy_vcpu_info to the header where vcpu_info_t
is defin
>>> On 14.09.15 at 04:32, wrote:
> changes in v5:
> 1) define macros for 0x1 and CPUID leaf5;
> 2) add a statement stating that this patch is independent of the
> previous ones.
This statement doesn't belong in the commit message, i.e. should go
after the first ---.
> --- a/xen/arch/x86/a
Hi,
>From the commit title, it's not clear that you are touching the PSCI code.
I would rewrite it like:
"xen/arm: psci: use SMC64 function ID when available on ARM64"
On 05/10/15 16:27, Brijesh Singh wrote:
> As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
> call functio
Ian Campbell writes ("[PATCH OSSTEST] make-flight: Don't bother testing
linux-3.10 on ARM."):
> The earliest version which boots on the hardware in the colo is v3.16+
> from the current linux-arm-xen branch.
>
> However in the h/w in the Cambridge instance works ok with linux-3.14
> and linux-3.1
El 11/09/15 a les 21.32, Julien Grall ha escrit:
> The minimal size of request in the block framework is always PAGE_SIZE.
> It means that when 64KB guest is support, the request will at least be
> 64KB.
>
> Although, if the backend doesn't support indirect grant (such as QDISK
> in QEMU), a ring
>>> On 17.09.15 at 17:19, wrote:
> On 14/09/15 03:32, Wei Wang wrote:
>> --- a/xen/include/xen/kernel.h
>> +++ b/xen/include/xen/kernel.h
>> @@ -43,6 +43,29 @@
>> #define MAX(x,y) ((x) > (y) ? (x) : (y))
>>
>> /**
>> + * clamp - return a value clamped to a given range with strict typechecking
The earliest version which boots on the hardware in the colo is v3.16+
from the current linux-arm-xen branch.
However in the h/w in the Cambridge instance works ok with linux-3.14
and linux-3.16.
We already skip linux branches 3.4 and earlier, so just add 3.10 too.
Signed-off-by: Ian Campbell
-
On Fri, 2 Oct 2015, Ian Campbell wrote:
> On Wed, 2015-09-30 at 16:45 +0100, Stefano Stabellini wrote:
>
> > QEMU is going to setuid and setgid to the user ID and the group ID of
> > the specified user, soon after initialization, before starting to deal
> > with any guest IO.
>
> Can you confirm
flight 62647 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62647/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 63e1c23b225578efdaca714a81055eadb0a07cec
baseline version:
ovmf ddd89cd50dd3a989e58a75ed38011168e3e
On 04/10/15 21:25, Tamas K Lengyel wrote:
> Currently mem-sharing can be performed on a page-by-page base from the control
> domain. However, when completely deduplicating (cloning) a VM, this requires
> at least 3 hypercalls per page. As the user has to loop through all pages up
> to max_gpfn, thi
On Tue, 2015-09-08 at 10:24 +0100, Ian Campbell wrote:
> grub-xen
>
>
> Needs much better docs.
>
> ACTION: I agreed to move the text of my blog post somewhere more
> obvious.
I did this on the last doc day: http://wiki.xen.org/wiki/PvGrub2
Ian.
___
As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
call function ID parameter should be set to SMC64 version.
Signed-off-by: Brijesh Singh
---
xen/arch/arm/psci.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/psci.c b/xen/arch/
flight 62645 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62645/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs.
El 11/09/15 a les 21.31, Julien Grall ha escrit:
> The code to get a request is always the same. Therefore we can factorize
> it in a single function.
>
> Signed-off-by: Julien Grall
Acked-by: Roger Pau Monné
___
Xen-devel mailing list
Xen-devel@lis
El 03/10/15 a les 2.34, Bob Liu ha escrit:
>
> On 10/03/2015 01:02 AM, Roger Pau Monné wrote:
>> El 05/09/15 a les 14.39, Bob Liu ha escrit:
>> In order to make this easier to review, do you think you can leave
>> blkfront_info as "info" for now, and do the renaming to dinfo in a later
>> patch. T
It looks to be missing in the policy file for the initial
domain. Eventually we may want to extend this access to
non-dom0 domains but for now it certainly dom0-only.
Reviewed-by: Boris Ostrovsky
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/flask/policy/policy/modules/xen/xen.te | 1 +
1 file
El 05/09/15 a les 14.39, Bob Liu ha escrit:
> Backend advertises "multi-queue-max-queues" to front, and then read back the
> final negotiated queues/rings from "multi-queue-num-queues" which is wrote by
> blkfront.
>
> Signed-off-by: Bob Liu
> ---
> drivers/block/xen-blkback/blkback.c |8 +++
1 - 100 of 210 matches
Mail list logo
