This fixes a regression introduced by commit ff913f68c9 ("x86/PV:
restrict permitted instructions during memory write emulation")
breaking namely 32-bit PV guests (which commonly use CMPXCHG8B for
certain page table updates).
Reported-by: Andrew Cooper
Signed-off-by: Jan Beulich
--- a/xen/arch/
Null selector loads into SS (possible in 64-bit mode only, and only in
rings other than ring 3) must not alter SS.DPL. (This was found to be
an issue on KVM, and fixed in Linux commit 33ab91103b.)
Further arch_set_info_hvm_guest() didn't make sure that the ASSERT()s
in hvm_set_segment_register() w
>>> On 19.01.17 at 18:44, wrote:
> On Thu, Jan 19, 2017 at 01:29:15AM -0700, Jan Beulich wrote:
>> >>> On 18.01.17 at 20:56, wrote:
>> > I am looking at rmrr_identity_mapping where the RMRR paddr get converted
>> > to pfn and then mapped with iommu.
>> > If ( rmrr->end_address & ~PAGE_SHIFT_MASK_
>>> On 19.01.17 at 18:10, wrote:
> --- a/xen/common/kexec.c
> +++ b/xen/common/kexec.c
> @@ -1182,7 +1182,8 @@ static int kexec_status(XEN_GUEST_HANDLE_PARAM(void)
> uarg)
> if ( kexec_load_get_bits(status.type, &base, &bit) )
> return -EINVAL;
>
> -return test_bit(bit, &kexec
On January 18, 2017 5:38 PM, Jan Beulich wrote:
On 18.01.17 at 05:57, wrote:
>> Attached was my earlier comment:
>>
>> --
>>> >>> On 20.12.16 at 06:37, wrote:
>>> >> From: Xuquan (Quan Xu) [mailto:xuqu...@huawei.com]
>>> >> Sent: Friday, December 16, 2016 5:40 PM
>>> >> -if (pt_vect
>>> On 20.01.17 at 05:06, wrote:
> On 1/19/17 8:34 PM, Daniel Kiper wrote:
>> Subsequent patches introducing relocatable early boot code play with
>> page tables using 2 MiB huge pages. If load address is not aligned at
>> 2 MiB then code touching such page tables must have special cases for
>> st
c/s ff913f6 "x86/PV: restrict permitted instructions during memory write
emulation" added an x86_insn_is_mem_write() restriction to all PV instructions
which trap for emulation because of read-only mappings (pagetables, mmcfg and
msi-x intercepts).
Because of the way cmpxchg{8,16}b was decoded (be
>>> On 20.01.17 at 09:47, wrote:
> Jan, I can't follow vector classes.. could you explain more? Thanks..
For determining vector priority, the LAPIC uses only the high 4 bits.
Iirc this is well documented in the SDM.
Jan
___
Xen-devel mailing list
Xen
flight 104306 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/104306/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 19ca06bb84cafd661f7da34e9ca3c7ec6add1135
baseline version:
ovmf 5ab0ffc9f64f5a539a9bd
On January 16, 2017 1:26 PM, Tian, Kevin wrote:
>I cannot come up a valid reason for such situation (intack.vector is 0x30 while
>pt_vector is 0x38 from Chao's data). pt_update_irq is invoked before checking
>highest pending IRRs so pt_vector should be honored anyway.
>One possible reason is that b
Recently Jim asked me why he can use "xl mem-max" to raise the allowed
memory size of a domain in the hypervisor above the configured maxmem
limit of the domain, but not use "xl mem-set" to balloon the domain up
to this value later.
I thought libxl_domain_setmaxmem() being buggy as it doesn't modi
> From: Yi Sun
> Sent: Thursday, January 19, 2017 2:01 PM
>
> This patch creates L2 CAT feature document in doc/features/.
> It describes details of L2 CAT.
A good write-up, but still some improvements required. :-)
>
> Signed-off-by: Yi Sun
> ---
> docs/features/intel_psr_l2_cat.pandoc | 347
>>> On 20.01.17 at 02:34, wrote:
> @@ -100,20 +107,48 @@ multiboot2_header_start:
> gdt_boot_descr:
> .word 6*8-1
> .long sym_phys(trampoline_gdt)
> +.long 0 /* Needed for 64-bit lgdt */
> +
> +.align 4
> +vga_text_buffer:
> +.long 0xb8000
> +
> +
The information given in the xl man page for the mem-max command is
rather brief. Expand it in order to let the reader understand what it
is really doing.
As the related libxl function libxl_domain_setmaxmem() isn't much
clearer add a comment to it explaining the desired semantics.
Signed-off-by:
>>> On 20.01.17 at 09:52, wrote:
> @@ -2852,6 +2852,11 @@ x86_emulate(
> else if ( !(d & Mov) ) /* optimisation - avoid slow emulated read */
> {
> fail_if(lock_prefix ? !ops->cmpxchg : !ops->write);
> +
> +/* cmpxchg{8,16}b handles its own operand read.
flight 104298 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/104298/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeatfail like 104267
test-amd64-i386-xl-qemuu
BT, being encoded as DstBitBase just like BT{C,R,S}, nevertheless does
not write its (register or memory) operand and hence also doesn't allow
a LOCK prefix to be used.
At the same time CLAC/STAC have no need to explicitly check lock_prefix
- this is being taken care of by generic code.
Signed-of
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-qemuu-rhel6hvm-amd
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditio
On Fri, Jan 20, 2017 at 06:41:06AM +, Tian, Kevin wrote:
> > From: Roger Pau Monne [mailto:roger@citrix.com]
> > Sent: Friday, January 20, 2017 1:30 AM
> >
> > There's nothing wrong with allowing the domain to perform DMA transfers to
> > MMIO areas that it already can access from the CPU,
The predefined pattern rule works.
Signed-off-by: Wei Liu
---
tools/fuzz/x86_instruction_emulator/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/fuzz/x86_instruction_emulator/Makefile
b/tools/fuzz/x86_instruction_emulator/Makefile
index 20431b0..1777bf6 100644
--- a/tools/f
On Fri, Jan 20, 2017 at 01:49:46AM -0700, Jan Beulich wrote:
> >>> On 20.01.17 at 05:06, wrote:
> > On 1/19/17 8:34 PM, Daniel Kiper wrote:
> >> Subsequent patches introducing relocatable early boot code play with
> >> page tables using 2 MiB huge pages. If load address is not aligned at
> >> 2 Mi
On 20/01/17 09:54, Jan Beulich wrote:
On 20.01.17 at 09:52, wrote:
>> @@ -2852,6 +2852,11 @@ x86_emulate(
>> else if ( !(d & Mov) ) /* optimisation - avoid slow emulated read */
>> {
>> fail_if(lock_prefix ? !ops->cmpxchg : !ops->write);
>> +
>> +/*
On 20/01/17 08:23, Jan Beulich wrote:
> This fixes a regression introduced by commit ff913f68c9 ("x86/PV:
> restrict permitted instructions during memory write emulation")
> breaking namely 32-bit PV guests (which commonly use CMPXCHG8B for
> certain page table updates).
>
> Reported-by: Andrew Coo
On 20/01/17 10:10, Jan Beulich wrote:
> BT, being encoded as DstBitBase just like BT{C,R,S}, nevertheless does
> not write its (register or memory) operand and hence also doesn't allow
> a LOCK prefix to be used.
>
> At the same time CLAC/STAC have no need to explicitly check lock_prefix
> - this i
>>> On 20.01.17 at 11:39, wrote:
> On 20/01/17 09:54, Jan Beulich wrote:
> On 20.01.17 at 09:52, wrote:
>>> @@ -2852,6 +2852,11 @@ x86_emulate(
>>> else if ( !(d & Mov) ) /* optimisation - avoid slow emulated read
>>> */
>>> {
>>> fail_if(lock_prefix ? !ops->cm
On Thu, Jan 19, 2017 at 09:14:03PM +0100, Julien Grall wrote:
> Hello,
>
> On 19/01/2017 19:22, Stefano Stabellini wrote:
> > On Thu, 19 Jan 2017, Roger Pau Monné wrote:
> > > On Wed, Jan 18, 2017 at 07:13:23PM +, Julien Grall wrote:
> > > > Hi,
> > > >
> > > > On 18/01/17 19:05, Stefano Stab
>>> On 20.01.17 at 09:52, wrote:
Commenting on just the parts not replaced by the other patch.
> @@ -461,6 +484,53 @@ int main(int argc, char **argv)
> goto fail;
> printf("okay\n");
>
> +#ifdef __x86_64__
> +memset(&state, 0, sizeof(state));
> +printf("%-40s", "Testing l
On 20/01/17 09:26, Juergen Gross wrote:
> Recently Jim asked me why he can use "xl mem-max" to raise the allowed
> memory size of a domain in the hypervisor above the configured maxmem
> limit of the domain, but not use "xl mem-set" to balloon the domain up
> to this value later.
>
> I thought libx
Boris Ostrovsky writes ("Re: [linux-linus bisection] complete
test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages]"):
> On 01/19/2017 01:05 PM, Ian Jackson wrote:
> > This means that the bug is in commits which diverged before the last
> > pass of this test.
> >
> > (Did your filters get you
Hello,
On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
an EventID (the MSI payload or interrupt ID) to a pair of LPI number
and collection ID, which points to the target CPU.
This ma
Hi,
On 20/01/17 11:12, Julien Grall wrote:
> Hello,
>
> On 04/01/2017 22:47, Stefano Stabellini wrote:
>> On Thu, 22 Dec 2016, Andre Przywara wrote:
>>> Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
>>> an EventID (the MSI payload or interrupt ID) to a pair of LPI number
On Fri, Jan 20, 2017 at 02:46:47AM -0700, Jan Beulich wrote:
> >>> On 20.01.17 at 02:34, wrote:
> > @@ -100,20 +107,48 @@ multiboot2_header_start:
> > gdt_boot_descr:
> > .word 6*8-1
> > .long sym_phys(trampoline_gdt)
> > +.long 0 /* Needed for 64-bit lgdt */
> > +
>>> On 18.01.17 at 11:23, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Wednesday, January 18, 2017 5:38 PM
>>
>> >>> On 18.01.17 at 05:57, wrote:
>> > Attached was my earlier comment:
>> >
>> > --
>> >> >>> On 20.12.16 at 06:37, wrote:
>> >> >> From: Xuquan (Quan Xu) [mailt
Hi Stefano,
Sorry for the late answer, still going through my e-mail backlog.
On 06/01/2017 21:20, Stefano Stabellini wrote:
On Fri, 6 Jan 2017, Andre Przywara wrote:
It is also possible to end up calling mapti with an inexistent eventid
for host_devid. Could that be a problem?
Not at all. A
If a timeout is adjusted, print a log message. We are going to want
to reuse this logic in a moment.
Do the defaulting in $adjust->() rather than passing 1 as a default
to the lookup functions, which is slightly neater.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 10 +-
1 f
Currently this has no real effect, because the only place where a
timeout factor is specified is nested L1s and we do not run build
commands on those.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Osstest/TestSupport.pm b/Osstest/Test
This gives us a single place to say that a host is particularly slow.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index b8946da..1108dbd 100644
--- a/Osstest/TestSupport.pm
+++ b/Osstest
Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104237: regressions -
FAIL"):
> I would not be surprised that it takes 2.5 hours for a make allmodules
> on both the Cubietruck and Arndale.
...
> So I can see 2 solutions:
> 1) Increase the timeout
> 2) Only build the kernel on
The said file needs the two header files.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
---
tools/fuzz/x86_instruction_emulator/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/fuzz/x86_instruction_emulator/Makefile
b/tools/fuzz/x86_instruction_emulator/Makefile
index 1777bf6.
This is a basic program to call into the unified fuzzing function.
Hook it up into build system so that we can always build test it.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
---
.gitignore | 1 +
And rename README to README.oss-fuzz.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
---
tools/fuzz/README.afl | 27 +++
tools/fuzz/{README => README.oss-fuzz} | 0
2 files changed, 27 insertions(+)
cr
Provide simple stub programs for AFL fuzzer. For usage, please see README.afl.
This series doesn't aim to improve fuzzing targets. It is just demonstration
for how we could use the same fuzzing code for both oss-fuzz and AFL.
The stub programs are identical in libefl and x86 emulator at the momen
And hook it up into build system.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
---
.gitignore| 1 +
tools/fuzz/libelf/Makefile| 7 +-
tools/fuzz/libelf/afl-libelf-fuzzer.c | 42 +++
Hi Andre,
On 20/01/2017 12:27, Andre Przywara wrote:
On 20/01/17 11:12, Julien Grall wrote:
Hello,
On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
an EventID (the MSI payload or i
I currently have this working well enough to run d-i and install the
host. I'm running a commissioning flight on both softiron boxes
(laxton0, laxton1).
If this works well enough I will push this seris to osstest pretest
and, assuming that it passes, put laxton* into production.
Note that I have
This is helpful for playing around with stretch, which seems to use
this option by default.
Signed-off-by: Ian Jackson
---
ts-host-install | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ts-host-install b/ts-host-install
index ecf5f0b..99ba130 100755
--- a/ts-host-install
+++
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 5eecf92..52527bf 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/Debian.pm
@@ -67,8 +67,9 @@ sub debian_boot_setup ($;$) {
my
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 4
1 file changed, 4 insertions(+)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index d0aabb5..444f80b 100755
--- a/mg-debian-installer-update
+++ b/mg-debian-installer-update
@@ -62,6 +62,7 @@ tftpdiversion
Debian #778564 remains open.
Signed-off-by: Ian Jackson
---
ts-host-install | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ts-host-install b/ts-host-install
index 99ba130..770c51b 100755
--- a/ts-host-install
+++ b/ts-host-install
@@ -135,7 +135,7 @@ END
my $done
No functional change.
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index bb1ae62..00cc735 100755
--- a/mg-debian-installer-update
+++ b/mg-debian-installe
UEFI uses vfat for the boot partiton.
This also means we need some charset modules.
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index 12586f8..079d3e8 100755
--- a/mg-debia
No other change
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 1 +
1 file changed, 1 insertion(+)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index 00cc735..d0aabb5 100755
--- a/mg-debian-installer-update
+++ b/mg-debian-installer-update
@@ -70,6 +70,7 @@
If mg-debian-installer-update decided not to provide an initramfs.deb,
just skip that.
No functional change with earlier d-i fetches produced by existing
versions of mg-debian-installer-update.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 6 +-
1 file changed, 5 insertions(+), 1 delet
Our ARM64 softiron boxes need these to find their network and disks.
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index 444f80b..12586f8 100755
--- a/mg-debian-installer-upd
Filesystem drivers now refer to this.
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 1 +
1 file changed, 1 insertion(+)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index 079d3e8..82a1804 100755
--- a/mg-debian-installer-update
+++ b/mg-debian-installer-upd
Introduce private function $kdeb->(). No functional change.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 45 +
1 file changed, 29 insertions(+), 16 deletions(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 52527bf..5a083c2 100644
--
host_pxefile now returns undef if the specified $templatekey is not
configured, rather than defaulting to the plain PxeTemplates.
This is going to useful because we want host_pxefile not to hardcode
the default: with netgrub, the settings are all different.
If $templatekey is 'PxeTemplates' then
Debian bug #789798 remains open. I have pinged the blocking bug in
grub2, #792547.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 987c7c6..5cd6433 100644
--- a/Osstest/Debian.pm
+++
Some of the arm64 kernels have backports in subdirectories. So use a
find rune instead of a plain mv.
Signed-off-by: Ian Jackson
---
mg-debian-installer-update | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index 82a
git-ls-files | xargs perl -i~ -pe 's/\bsetup_pxeboot_/setup_netboot_/g'
git-ls-files | xargs perl -i~ -pe 's/\bsetup_pxelinux_/setup_netboot_/g'
No functional change.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 28 ++--
ts-host-install| 8
* Now it takes the tail of the template key (currently, normally
`Templates') rather than the whole of it (`PxeTemplates'); the
`Pxe' part is implied.
* Now it normally returns the whole path, including PxeDir, which the
caller is no longer expected to prepend. In any case, it supplies
th
UEFI grub netbooting is not PXE. Indeed PXE is a BIOS thing only.
No functional change other than to messages.
Signed-off-by: Ian Jackson
---
INSTALL.production | 10 +-
Osstest/Debian.pm | 2 +-
Osstest/TestSupport.pm | 6 +++---
README | 4 ++--
mg-hosts
Use mkdir -p in both cases. Otherwise these late_commands may fail.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index dacefb3..987c7c6 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/
This used to be mg-pxe-loader-update, but it updates grub and not
anything to do with PXE.
Signed-off-by: Ian Jackson
---
README | 2 +-
mg-netgrub-loader-update | 84
mg-pxe-loader-update | 84 --
* When expanding netboot filenames, look for NetGrub config keys
rather than Pxe filenames. Currently this only affects mg-hosts
because the files are created by setup_grub_efi_bootcfg, and the
files are of course referred to only by the actual netboot grub
image (which may be made by mg-n
No functional change.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 31 +++
1 file changed, 19 insertions(+), 12 deletions(-)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index bb72fe5..990ddbc 100644
--- a/Osstest/TestSupport.pm
+++ b/Osste
No functional change.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 39 +++
1 file changed, 27 insertions(+), 12 deletions(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 4c73318..f496354 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/Debian.pm
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 0137fc4..06918ef 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/Debian.pm
@@ -1124,12 +1124,15 @@ in-target tar -C /boot -xaf /tmp/dtb
No functional change.
Signed-off-by: Ian Jackson
---
mg-netgrub-loader-update | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mg-netgrub-loader-update b/mg-netgrub-loader-update
index ca8abcb..9eb20d5 100755
--- a/mg-netgrub-loader-update
+++ b/mg-netgrub-loader-update
This applies to NetGrub too. Honour the old setting for
compatibility.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 6 --
README | 2 +-
mg-hosts| 2 +-
production-config | 2 +-
production-config-cambridge | 2 +-
5 files c
Signed-off-by: Ian Jackson
---
mg-netgrub-loader-update | 12
1 file changed, 12 insertions(+)
diff --git a/mg-netgrub-loader-update b/mg-netgrub-loader-update
index 73deb19..22ef67c 100755
--- a/mg-netgrub-loader-update
+++ b/mg-netgrub-loader-update
@@ -10,6 +10,18 @@
# (where EE
No functional change.
Signed-off-by: Ian Jackson
---
mg-netgrub-loader-update | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mg-netgrub-loader-update b/mg-netgrub-loader-update
index 9eb20d5..ec6dfd3 100755
--- a/mg-netgrub-loader-update
+++ b/mg-netgrub-loader-update
@@
No functional change.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 6 +++---
mg-hosts | 14 +++---
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index fde796a..bb72fe5 100644
--- a/Osstest/TestSu
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index 06918ef..acc4618 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/Debian.pm
@@ -890,6 +890,8 @@ d-i grub-installer/only_debian boolean true
d-i grub-inst
Was ./mg-hosts mkpxedir, but it is more general.
Signed-off-by: Ian Jackson
---
README | 4 ++--
README.dev | 2 +-
mg-hosts | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/README b/README
index 01644b0..91d0328 100644
--- a/README
+++ b/README
@@ -538,8 +538,8 @@
This will be wrong when this is used for netgrub too.
Only functional change is to log outputs.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index 6d0f967..9be40a2 100644
Newer kernels may need a newer linux-base. This call has the happy
side effect of adding backports to its sources.list, which is also
generally needed.
Signed-off-by: Ian Jackson
---
Osstest/Debian.pm | 5 +
1 file changed, 5 insertions(+)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
Signed-off-by: Ian Jackson
---
make-flight| 9 ++---
mfi-common | 27 +++
mg-debian-installer-update | 1 +
3 files changed, 30 insertions(+), 7 deletions(-)
diff --git a/make-flight b/make-flight
index a374884..f513b80 100755
--- a/m
* Abolish setup_grub_efi_bootcfg and use setup_netboot_bootcfg
instead. The latter function now expects to be given a config file
for the host's bootloader. For a UEFI host, that's a grub config
file, which it will write to the configured NetGrub location for the
specific host.
* Consequ
Signed-off-by: Ian Jackson
---
mg-netgrub-loader-update | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/mg-netgrub-loader-update b/mg-netgrub-loader-update
index 21157a2..73deb19 100755
--- a/mg-netgrub-loader-update
+++ b/mg-netgrub-loader-update
@@ -93,11 +93,17 @
>>> On 20.01.17 at 12:43, wrote:
> On Fri, Jan 20, 2017 at 02:46:47AM -0700, Jan Beulich wrote:
>> >>> On 20.01.17 at 02:34, wrote:
>> > @@ -100,20 +107,48 @@ multiboot2_header_start:
>> > gdt_boot_descr:
>> > .word 6*8-1
>> > .long sym_phys(trampoline_gdt)
>> > +.l
On 20/01/17 08:26, Jan Beulich wrote:
> Null selector loads into SS (possible in 64-bit mode only, and only in
> rings other than ring 3) must not alter SS.DPL. (This was found to be
> an issue on KVM, and fixed in Linux commit 33ab91103b.)
>
> Further arch_set_info_hvm_guest() didn't make sure tha
Hi Royger,
On 20/01/2017 12:01, Roger Pau Monné wrote:
On Thu, Jan 19, 2017 at 09:14:03PM +0100, Julien Grall wrote:
On 19/01/2017 19:22, Stefano Stabellini wrote:
On Thu, 19 Jan 2017, Roger Pau Monné wrote:
On Wed, Jan 18, 2017 at 07:13:23PM +, Julien Grall wrote:
Hi,
On 18/01/17 19:05
This run is configured for baseline tests only.
flight 68400 linux-3.18 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68400/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm
On Fri, Jan 20, 2017 at 05:40:55AM -0700, Jan Beulich wrote:
> >>> On 20.01.17 at 12:43, wrote:
> > On Fri, Jan 20, 2017 at 02:46:47AM -0700, Jan Beulich wrote:
> >> >>> On 20.01.17 at 02:34, wrote:
[...]
> >> > +.Lefi_multiboot2_proto:
> >> > +/* Zero EFI SystemTable and EFI ImageHandl
On Thu, Jan 19, 2017 at 04:29:19PM -0800, Stefano Stabellini wrote:
> On Thu, 19 Jan 2017, Konrad Rzeszutek Wilk wrote:
> > On Thu, Jan 19, 2017 at 06:58:46PM -0500, Boris Ostrovsky wrote:
> > > On 01/19/2017 01:39 PM, Stefano Stabellini wrote:
> > > > In xen_swiotlb_map_page and xen_swiotlb_map_sg
On Fri, Jan 20, 2017 at 10:54:18AM +0100, Juergen Gross wrote:
> The information given in the xl man page for the mem-max command is
> rather brief. Expand it in order to let the reader understand what it
> is really doing.
>
> As the related libxl function libxl_domain_setmaxmem() isn't much
> cl
On Fri, Jan 20, 2017 at 11:08:54AM +, Andrew Cooper wrote:
> On 20/01/17 09:26, Juergen Gross wrote:
Cc-ing Daniel as he wrote the Xen Balloon memory hotplug code.
> > Recently Jim asked me why he can use "xl mem-max" to raise the allowed
> > memory size of a domain in the hypervisor above th
>>> On 20.01.17 at 14:46, wrote:
> On Fri, Jan 20, 2017 at 05:40:55AM -0700, Jan Beulich wrote:
>> >>> On 20.01.17 at 12:43, wrote:
>> > On Fri, Jan 20, 2017 at 02:46:47AM -0700, Jan Beulich wrote:
>> >> >>> On 20.01.17 at 02:34, wrote:
>> >> > --- a/xen/include/asm-x86/config.h
>> >> > +++ b/xe
>> For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work
>> for all operating systems, not just Linux. (Lets please not waste time
>> building a somewhat-square wheel which only fits on a Linux shaped axle :) )
What about PVH dom0? I suspect we will have the same problem with A
On Fri, Jan 20, 2017 at 02:10:33PM +0100, Julien Grall wrote:
> Hi Royger,
>
> On 20/01/2017 12:01, Roger Pau Monné wrote:
> > On Thu, Jan 19, 2017 at 09:14:03PM +0100, Julien Grall wrote:
> In case of ARM, Xen does not use any PCI devices (no PCI UART) itself so
> scanning before hand is not nece
On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote:
>
> >> For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work
> >> for all operating systems, not just Linux. (Lets please not waste time
> >> building a somewhat-square wheel which only fits on a Linux shaped axle
On 20/01/17 15:27, Roger Pau Monné wrote:
> On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote:
>>
For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work
for all operating systems, not just Linux. (Lets please not waste time
building a somewhat-square w
On 17/01/17 17:29, Paul Durrant wrote:
> ...as a set of hypercalls to be used by a device model.
>
> As stated in the new docs/designs/dm_op.markdown:
>
> "The aim of DMOP is to prevent a compromised device model from
> compromising domains other then the one it is associated with. (And is
> theref
On 01/20/2017 09:27 AM, Roger Pau Monné wrote:
> On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote:
For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work
for all operating systems, not just Linux. (Lets please not waste time
building a somewhat-square
On Fri, Jan 20, 2017 at 07:10:32AM -0700, Jan Beulich wrote:
> >>> On 20.01.17 at 14:46, wrote:
> > On Fri, Jan 20, 2017 at 05:40:55AM -0700, Jan Beulich wrote:
> >> >>> On 20.01.17 at 12:43, wrote:
> >> > On Fri, Jan 20, 2017 at 02:46:47AM -0700, Jan Beulich wrote:
> >> >> >>> On 20.01.17 at 02:
flight 104327 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/104327/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-checkfail like 104283
test-armhf-armhf-libvirt-qcow2 1
On 19/01/17 17:10, Eric DeVolder wrote:
> When checking kexec_flags bit corresponding to the
> requested image, ensure that 0 or 1 is returned.
>
> Signed-off-by: Eric DeVolder
Reviewed-by: Andrew Cooper and committed. I
dropped the commit while doing so
~Andrew
__
> -Original Message-
> From: Andrew Cooper
> Sent: 20 January 2017 14:35
> To: Paul Durrant ; xen-de...@lists.xenproject.org
> Cc: Ian Jackson ; Jennifer Herbert
> ; Daniel De Graaf ;
> Wei Liu ; Jan Beulich
> Subject: Re: [PATCH v4 1/8] public / x86: Introduce __HYPERCALL_dm_op...
>
> On
On 17/01/17 17:29, Paul Durrant wrote:
> The definitions of HVM_IOREQSRV_BUFIOREQ_* have to persist as they are
> already in use by callers of the libxc interface.
>
> Suggested-by: Jan Beulich
> Signed-off-by: Paul Durrant
Reviewed-by: Andrew Cooper
___
1 - 100 of 217 matches
Mail list logo
