On 03/09/2018 09:10 AM, Olaf Hering wrote:
Add an option to control when vTSC emulation will be activated for a
domU with tsc_mode=default. Without such option each TSC access from
domU will be emulated, which causes a significant perfomance drop for
workloads that make use of rdtsc.
Add a new
flight 120338 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120338/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvops 6 kernel-build fail REGR. vs. 118294
build-i386-pvops
flight 120318 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120318/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 14 xen-boot/l1 fail REGR. vs. 120095
flight 120372 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120372/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
On 03/09/2018 01:41 PM, Andrew Cooper wrote:
On 09/03/2018 18:05, Boris Ostrovsky wrote:
On 02/26/2018 06:30 PM, Andrew Cooper wrote:
On 26/02/2018 19:44, Boris Ostrovsky wrote:
On 02/26/2018 02:12 PM, Andrew Cooper wrote:
On 20/02/18 11:58, Andrew Cooper wrote:
This rats nest was
Extend API for managing bitmaps. Each bitmap is now represented by a
generic struct xc_sr_bitmap.
Switch the existing populated_pfns to this API.
Signed-off-by: Olaf Hering
Acked-by: Wei Liu
---
tools/libxc/xc_sr_common.c | 41 +
Using superpages on the receiving dom0 will avoid performance regressions.
Olaf
TODO:
send 1G batches on HVM to help allocator on dst dom0
v11:
rebase to and for 4.11
v10:
coding style in xc_sr_bitmap API
reset bitmap size on free
check for empty bitmap in xc_sr_bitmap API
add comment to
The macros SUPERPAGE_2MB_SHIFT and SUPERPAGE_1GB_SHIFT will be used by
other code in libxc. Move the macros to a header file.
Signed-off-by: Olaf Hering
Acked-by: Wei Liu
---
tools/libxc/xc_dom_x86.c | 5 -
tools/libxc/xc_private.h | 5 +
2 files
All this information is now covered in SUPPORT.md.
Most of the emulated hardware is obvious a couple of the items are
worth pointing out specifically.
"xen_disk" is listed under "Blkback"
"...the PCI host bridge and the PIIX3 chipset...": This statement is
redundant -- the PCI host bridge is a
s/fo/fo; while we're here.
Signed-off-by: George Dunlap
---
This is a candidate for backport to 4.10.
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
CC: Jan Beulich
CC: Tim
On 09/03/18 16:29, Jan Beulich wrote:
On 05.03.18 at 10:50, wrote:
>> @@ -120,11 +121,24 @@ unsigned int flush_area_local(const void *va, unsigned
>> int flags)
>> else
>> {
>> u32 t = pre_flush();
>> -unsigned long cr4 =
On 02/26/2018 06:30 PM, Andrew Cooper wrote:
On 26/02/2018 19:44, Boris Ostrovsky wrote:
On 02/26/2018 02:12 PM, Andrew Cooper wrote:
On 20/02/18 11:58, Andrew Cooper wrote:
This rats nest was discovered when finding that MSR_TSC_AUX leaked into PV
guests. It is RFC because I haven't done
Hi Andre,
On 05/03/18 16:04, Andre Przywara wrote:
The ARM arch code requires an interrupt controller emulation to implement
vgic_clear_pending_irqs(), although it is suspected that it is actually
not necessary. Go with a stub for now to make the linker happy.
The implementation of that
Hi Andre,
On 05/03/18 16:04, Andre Przywara wrote:
This patch allocates and initializes the data structures used to model
the vgic distributor and virtual cpu interfaces. At that stage the
number of IRQs and number of virtual CPUs is frozen.
Implement the various functions that the Xen arch
Hi Andre,
On 05/03/18 16:04, Andre Przywara wrote:
map_resources is the last initialization step needed before the first
VCPU is run. At that stage the code stores the MMIO base addresses used.
Also it registers the respective register frames with the MMIO framework.
This is based on Linux
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.16a-rc5-tag
xen: fix for V4.16-rc5
It contains just one fix for the correct error handling after a negative
rc from device_register().
Thanks.
Juergen
Hi Andre,
On 05/03/18 16:04, Andre Przywara wrote:
Enable the VGIC operation by properly initialising the registers
in the hypervisor GIC interface.
This is based on Linux commit f7b6985cc3d0, written by Eric Auger.
Signed-off-by: Andre Przywara
Would you mind to
Hi,
On 05/03/18 16:04, Andre Przywara wrote:
At the moment we allocate exactly one page for struct vcpu on ARM, also
have a check in place to prevent it growing beyond 4KB.
As the struct includes the state of all 32 private (per-VCPU) interrupts,
we are at 3840 bytes on arm64 at the moment
flight 120360 rumprun real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120360/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumprun6 rumprun-buildfail REGR. vs. 106754
build-amd64-rumprun
> On 9. Mar 2018, at 22:57, Michael Young wrote:
>
> I have had a go at fixing the patch and my revised attempt is attached. I
> suspect it could be tidied up, but it works for me.
Thank you for giving this another go. What is the key difference to the
previous patch
flight 120336 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120336/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 6 xen-install fail REGR. vs. 12
On Mon, 12 Feb 2018, Wei Liu wrote:
On Fri, Feb 09, 2018 at 09:20:33AM +, Christian Lindig wrote:
On 8. Feb 2018, at 18:24, Wei Liu wrote:
Christian, do you have any idea when you can look into fixing the
safe-string patch?
Sorry, I can’t make a promise because
On 09/03/18 13:35, awokd wrote:
> On Fri, March 9, 2018 11:52 am, awokd wrote:
>
>> Xen on ARM might be a more reasonable starting point but I'm not sure
>> that would provide enough horsepower to drive a workstation
That's indeed an issue. There are ARM64 SoCs which are very capable and
could
On Fri, 9 Mar 2018, Christian Lindig wrote:
On 9. Mar 2018, at 22:57, Michael Young wrote:
I have had a go at fixing the patch and my revised attempt is attached. I
suspect it could be tidied up, but it works for me.
Thank you for giving this another go. What is
On Fri, 9 Mar 2018, Julien Grall wrote:
> Furthermore, the workaround is not in Linux upstream and I doubt this will be
> accepted as it is. So I am not convinced that we should modify Xen interface
> for that.
>
> Anyway, given that your silicon is going to be respined, then you probably
> want
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Gross
commit 71c208dd54ab971036d83ff6d9837bae4976e623 upstream.
Older Xen versions (4.5 and before) might have problems migrating pv
guests with MSR_IA32_SPEC_CTRL
flight 120351 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120351/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539
Tests which did not
On Fri, Mar 09, Juergen Gross wrote:
> So how does this work?
No idea, at least this output differs:
abuild@latitude:~> readelf -Wa /usr/lib64/libpython2.7.so | grep dlsym
003e5e08 00d90007 R_X86_64_JUMP_SLOT
dlsym@GLIBC_2.2.5 + 0
217:
On 09/03/2018, 11:07, "Jan Beulich" wrote:
>>> On 08.03.18 at 18:37, wrote:
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -620,6 +620,7 @@ Note that other devices are available but not
security supported.
>
> ### x86/Emulated
On 09/03/2018, 11:08, "Jan Beulich" wrote:
>>> On 08.03.18 at 19:07, wrote:
> @Jan: this should be backported to 4.10 also
I'll try to remember that, but let's first get it into master (and as
you've likely seen, I'm not
On 09/03/2018, 11:31, "Julien Grall" wrote:
Hi Lars,
On 08/03/18 17:37, Lars Kurth wrote:
> x86/Emulated platform devices (QEMU):
> - Aded PCI host bridge (as in xen.git:docs/misc/qemu-xen-security)
> New: x86/Emulated Storage Image Formats
>
On 03/09/2018 10:31 AM, Julien Grall wrote:
> Hi Lars,
>
> On 08/03/18 17:37, Lars Kurth wrote:
>> x86/Emulated platform devices (QEMU):
>> - Aded PCI host bridge (as in xen.git:docs/misc/qemu-xen-security)
>> New: x86/Emulated Storage Image Formats
>> - Added raw, qcow, qcow2, vhd (as in
On 03/09/2018 10:34 AM, Lars Kurth wrote:
>
>
> On 09/03/2018, 11:32, "George Dunlap" wrote:
>
> On 03/08/2018 06:07 PM, Lars Kurth wrote:
> >
> > On 08/03/2018, 18:44, "Ian Jackson" wrote:
> >
> > Lars Kurth writes
>>> On 08.03.18 at 23:24, wrote:
> flight 120287 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/120287/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>
On Fri, Mar 09, 2018 at 10:38:00AM -, awokd wrote:
> On Fri, March 9, 2018 10:03 am, Andrew Cooper wrote:
> > On 09/03/2018 09:37, awokd wrote:
>
> >
> > Xen currently has x86 and ARM as supported architectures, so there is a
> > reasonable split between common and arch-specific code. As a
On Fri, Mar 09, Olaf Hering wrote:
> abuild@latitude:~> readelf -Wa /usr/lib64/libpython2.7.so | grep dlsym
> 003e5e08 00d90007 R_X86_64_JUMP_SLOT
> dlsym@GLIBC_2.2.5 + 0
>217: 0 FUNCGLOBAL DEFAULT UND dlsym@GLIBC_2.2.5
> (10)
On Fri, March 9, 2018 11:25 am, Andrew Cooper wrote:
> I expect that once the ball is rolling, it will pick up momentum, given
> the interest I've already seen on IRC. You probably want to hang out on
> freenode #xendevel
Thanks again for your and the other replies.
I have some hardware
On Fri, March 9, 2018 11:24 am, Andre Przywara wrote:
>
> If you are serious about it, you need a team. Which is about to stay
> around! At least two people, who both know the architecture *and* Xen well.
> And it will probably take them more than a year to get something
> into a state where you
On Fri, Mar 9, 2018 at 11:24 AM, Andre Przywara wrote:
> Hi,
>
> On 09/03/18 10:38, awokd wrote:
>> On Fri, March 9, 2018 10:03 am, Andrew Cooper wrote:
>>> On 09/03/2018 09:37, awokd wrote:
>>
>>>
>>> Xen currently has x86 and ARM as supported architectures, so there is a
Hi Peng,
On 09/03/18 09:05, Peng Fan wrote:
On Thu, Mar 08, 2018 at 03:13:50PM +, Julien Grall wrote:
On 08/03/18 12:43, Peng Fan wrote:
There are a major difference between Dom0 and DomU in your setup.
Dom0 vCPUs are pinned to a specific pCPU, so they can't move around.
For DomU, each
On 03/09/2018 10:07 AM, Jan Beulich wrote:
On 08.03.18 at 18:37, wrote:
>> --- a/SUPPORT.md
>> +++ b/SUPPORT.md
>> @@ -620,6 +620,7 @@ Note that other devices are available but not security
>> supported.
>>
>> ### x86/Emulated platform devices (QEMU):
>>
>> +
On 03/08/2018 06:07 PM, Lars Kurth wrote:
>
> On 08/03/2018, 18:44, "Ian Jackson" wrote:
>
> Lars Kurth writes ("[PATCH] Move missing items from
> docs/misc/qemu-xen-security to SUPPORT.md"):
> > x86/Emulated platform devices (QEMU):
> > - Aded PCI host
>>> On 09.03.18 at 11:28, wrote:
> On 09/03/2018, 11:07, "Jan Beulich" wrote:
>
> >>> On 08.03.18 at 18:37, wrote:
> > --- a/SUPPORT.md
> > +++ b/SUPPORT.md
> > @@ -620,6 +620,7 @@ Note that other devices are
Hi,
On 09/03/18 10:38, awokd wrote:
> On Fri, March 9, 2018 10:03 am, Andrew Cooper wrote:
>> On 09/03/2018 09:37, awokd wrote:
>
>>
>> Xen currently has x86 and ARM as supported architectures, so there is a
>> reasonable split between common and arch-specific code. As a start, you'd
>> need to
On 09/03/18 10:38, awokd wrote:
> On Fri, March 9, 2018 10:03 am, Andrew Cooper wrote:
>> On 09/03/2018 09:37, awokd wrote:
>> Xen currently has x86 and ARM as supported architectures, so there is a
>> reasonable split between common and arch-specific code. As a start, you'd
>> need to implement
Eduardo Habkost writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict
until just before os_setup_post"):
> On Thu, Mar 08, 2018 at 05:39:09PM +, Ian Jackson wrote:
> [...]
> > diff --git a/vl.c b/vl.c
> > +xen_setup_post();
>
> I don't think we should have accelerator-specific code
>>> On 09.03.18 at 11:03, wrote:
> On 09/03/2018 09:37, awokd wrote:
>> Lastly, along the lines of those who fail to learn from history are doomed
>> to repeat it, what happened to the Xen PPC port a decade ago? I found an
>> archive of the xen-ppc-devel mailing list
On 09/03/2018, 11:32, "George Dunlap" wrote:
On 03/08/2018 06:07 PM, Lars Kurth wrote:
>
> On 08/03/2018, 18:44, "Ian Jackson" wrote:
>
> Lars Kurth writes ("[PATCH] Move missing items from
On 09/03/2018, 11:38, "George Dunlap" wrote:
On 03/09/2018 10:34 AM, Lars Kurth wrote:
>
> On 09/03/2018, 11:32, "George Dunlap" wrote:
>
> On 03/08/2018 06:07 PM, Lars Kurth wrote:
> >
> > @Jan:
On 09/03/18 11:41, Jan Beulich wrote:
On 06.03.18 at 21:24, wrote:
>> Currently with then native toolchain on Debian Jessie ./test_x86_emulator
>> yeilds:
>>
>> Testing AVX2 256bit single native execution...okay
>> Testing AVX2 256bit single 64-bit code
Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict until
just before os_setup_post"):
> How about this ?
And here's the corresponding change to the Xen-specific patch.
From d6140681a877c4d468c4fcf5cac075cdffbea22c Mon Sep 17 00:00:00 2001
From: Ian Jackson
Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict until
just before os_setup_post"):
> Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict until
> just before os_setup_post"):
> > How about this ?
>
> And here's the corresponding change to the
Hi Lars,
On 08/03/18 17:37, Lars Kurth wrote:
x86/Emulated platform devices (QEMU):
- Aded PCI host bridge (as in xen.git:docs/misc/qemu-xen-security)
New: x86/Emulated Storage Image Formats
- Added raw, qcow, qcow2, vhd (as in xen.git:docs/misc/qemu-xen-security)
Is there any reason to be
On Fri, March 9, 2018 10:03 am, Andrew Cooper wrote:
> On 09/03/2018 09:37, awokd wrote:
>
> Xen currently has x86 and ARM as supported architectures, so there is a
> reasonable split between common and arch-specific code. As a start, you'd
> need to implement enough of the arch stubs to make
flight 120312 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120312/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-3 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 119227
>>> On 09.03.18 at 11:30, wrote:
> On 03/09/2018 10:07 AM, Jan Beulich wrote:
> On 08.03.18 at 18:37, wrote:
>>> --- a/SUPPORT.md
>>> +++ b/SUPPORT.md
>>> @@ -620,6 +620,7 @@ Note that other devices are available but not security
>>>
Please update the qemu-xen tree to include 75e5b70e6b ("memfd: fix
configure test"). Currently xen.git#staging fails like this:
xen-staging/tools/qemu-xen-dir/util/memfd.c:40:12: error: static declaration of
'memfd_create' follows non-static declaration
Thank you.
Olaf
signature.asc
>>> On 06.03.18 at 21:24, wrote:
> Introduce common helpers for saving and restoring FPU state. During
> emul_test_init(), calculate whether to use xsave or fxsave, and tweak the
> existing mxcsr_mask logic to avoid using another large static buffer.
>
>
>>> On 06.03.18 at 21:24, wrote:
> Currently with then native toolchain on Debian Jessie ./test_x86_emulator
> yeilds:
>
> Testing AVX2 256bit single native execution...okay
> Testing AVX2 256bit single 64-bit code sequence...[line 933] failed!
>
> The bug is that
>>> On 06.03.18 at 21:24, wrote:
> --- a/tools/tests/x86_emulator/test_x86_emulator.c
> +++ b/tools/tests/x86_emulator/test_x86_emulator.c
> @@ -16,6 +16,53 @@
> #include "xop.h"
>
> #define verbose false /* Switch to true for far more logging. */
> +#define
>>> On 09.03.18 at 12:45, wrote:
> On 09/03/18 11:41, Jan Beulich wrote:
> On 06.03.18 at 21:24, wrote:
>>> Currently with then native toolchain on Debian Jessie ./test_x86_emulator
>>> yeilds:
>>>
>>> Testing AVX2 256bit single native
On Fri, Mar 09, 2018 at 12:05:18PM +0100, Olaf Hering wrote:
> Please update the qemu-xen tree to include 75e5b70e6b ("memfd: fix
> configure test").
Done. I've pushed the commit to qemu-xen staging.
Thanks for the report.
--
Anthony PERARD
___
Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict until
just before os_setup_post"):
> Eduardo Habkost writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict
> until just before os_setup_post"):
> > I don't think we should have accelerator-specific code in main(),
> > if
On Fri, March 9, 2018 12:04 pm, George Dunlap wrote:
> I'm all for encouraging people to jump into Xen, but I agree with
> Andre here, that you should really count the cost. I doubt this is
> the sort of thing a single person could really write and maintain unpaid on
> evenings and weekends.
Specifically https://en.wikipedia.org/wiki/POWER9.
Qubes user here. Due to the ongoing manufacturer lock-down of the x86
arch. and security vulnerabilities introduced by same, I'm looking into
hardware alternatives. One promising candidate appears to be the POWER
architecture.
What would it take
On Thu, Mar 08, 2018 at 03:13:50PM +, Julien Grall wrote:
>Hi,
>
>On 08/03/18 12:43, Peng Fan wrote:
>>I am not sure whether this issue cause DomU big/Little not work.
>
>Well, I would recommend to speak with NXP whether this errata affects
>TLB flush for Hypervisor Page-Table
On 09/03/18 09:34, Jan Beulich wrote:
On 09.03.18 at 06:23, wrote:
>>> From: Jan Beulich [mailto:jbeul...@suse.com]
>>> Sent: Thursday, March 8, 2018 9:39 PM
>>>
--- a/xen/include/asm-x86/domain.h
+++ b/xen/include/asm-x86/domain.h
@@ -622,7 +622,8 @@
On 09/03/2018 09:37, awokd wrote:
> Specifically https://en.wikipedia.org/wiki/POWER9.
>
> Qubes user here. Due to the ongoing manufacturer lock-down of the x86
> arch. and security vulnerabilities introduced by same, I'm looking into
> hardware alternatives. One promising candidate appears to be
>>> On 08.03.18 at 19:07, wrote:
> On 08/03/2018, 18:44, "Ian Jackson" wrote:
>
> Lars Kurth writes ("[PATCH] Move missing items from
> docs/misc/qemu-xen-security to SUPPORT.md"):
> > x86/Emulated platform devices (QEMU):
> > - Aded
>>> On 09.03.18 at 08:32, wrote:
> It seems to be solved by your patch !
Thanks for confirming; I'll take the liberty and add your Tested-by
then too.
Jan
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
>>> On 09.03.18 at 06:23, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, March 8, 2018 9:39 PM
>>
>> > --- a/xen/include/asm-x86/domain.h
>> > +++ b/xen/include/asm-x86/domain.h
>> > @@ -622,7 +622,8 @@ unsigned long pv_guest_cr4_fixup(const
>>> On 08.03.18 at 18:37, wrote:
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -620,6 +620,7 @@ Note that other devices are available but not security
> supported.
>
> ### x86/Emulated platform devices (QEMU):
>
> +Status, PCI host bridge: Supported
> Status,
On Wed, Mar 07, Juergen Gross wrote:
> On 07/03/18 13:06, ian.jack...@citrix.com wrote:
> > Juergen Gross writes ("Re: [PATCH] tools/xenstore: add libdl dependency to
> > libxenstore"):
> >> On 07/03/18 12:19, Ian Jackson wrote:
> >>> Juergen Gross writes ("[PATCH] tools/xenstore: add libdl
Offlining a CPU involves stopping the cpufreq governor. The on-demand
governor will kill the timer before letting generic code proceed, but
since that generally isn't happening on the subject CPU,
cpufreq_dbs_timer_resume() may run in parallel. If that managed to
invoke the timer handler, that
On 09/03/18 09:36, Olaf Hering wrote:
> On Wed, Mar 07, Juergen Gross wrote:
>
>> On 07/03/18 13:06, ian.jack...@citrix.com wrote:
>>> Juergen Gross writes ("Re: [PATCH] tools/xenstore: add libdl dependency to
>>> libxenstore"):
On 07/03/18 12:19, Ian Jackson wrote:
> Juergen Gross
>>> On 09.03.18 at 15:12, wrote:
> On Fri, Mar 09, 2018 at 01:18:36PM +, Andrew Cooper wrote:
>> At the moment, there is a tight coupling between the domid and the use of
>> DOMCRF_dummy. Instead of using DOMCRF_dummy, base the one relevent decision
>> on domid alone.
>>
>>> On 09.03.18 at 15:16, wrote:
> Reviewed-by: Wei Liu
Acked-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
On 03/09/2018 04:43 PM, Jan Beulich wrote:
On 09.03.18 at 17:30, wrote:
>> On 03/09/2018 04:25 PM, Jan Beulich wrote:
>> On 09.03.18 at 17:17, wrote:
--- a/xen/include/public/domctl.h
+++ b/xen/include/public/domctl.h
@@ -137,6
>>> On 09.03.18 at 15:13, wrote:
> On Fri, Mar 09, 2018 at 01:18:39PM +, Andrew Cooper wrote:
>> Neither domcr_flags nor config are used on either side. Drop them, making
>> {hvm,pv}_domain_initialise() symmetric with all the other domain/vcpu
>> initialise/destroy
>>> On 09.03.18 at 14:18, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -430,20 +430,37 @@ int arch_domain_create(struct domain *d, unsigned int
> domcr_flags,
> struct xen_arch_domainconfig *config)
> {
> bool
On Tue, Jan 16, 2018 at 02:12:27AM +0800, Luwei Kang wrote:
> This patch add a flag to enable Intel PT (Intel processor trace).
> Default value is 1 (enabled).
>
> Signed-off-by: Luwei Kang
> ---
> docs/misc/xen-command-line.markdown | 7 +++
>
The point was to document the counter part. Grep -w 1024 is not helpful.
Olaf___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On Fri, Feb 23, 2018 at 09:03:26PM +0100, Marek Marczykowski-Górecki wrote:
> On Fri, Feb 23, 2018 at 06:47:57PM +, Wei Liu wrote:
> > On Fri, Feb 09, 2018 at 12:14:03AM +0100, Marek Marczykowski-Górecki wrote:
> > > When fd=-1, no savefile will be written, but the domain will still be
> > >
Thanks, George! This includes part of Intel features. Chao is working on a
complete list of patch series and their status for all Intel features.
Best Regards
John Ji
-Original Message-
From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of George Dunlap
Sent: Saturday,
>>> On 09.03.18 at 14:18, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -426,8 +426,8 @@ static bool emulation_flags_ok(const struct domain *d,
> uint32_t emflags)
> return true;
> }
>
> -int arch_domain_create(struct domain *d,
On 09/03/18 16:49, George Dunlap wrote:
> On 03/09/2018 04:43 PM, Jan Beulich wrote:
> On 09.03.18 at 17:30, wrote:
>>> On 03/09/2018 04:25 PM, Jan Beulich wrote:
>>> On 09.03.18 at 17:17, wrote:
> --- a/xen/include/public/domctl.h
> +++
On 09/03/18 17:00, Jan Beulich wrote:
On 09.03.18 at 14:18, wrote:
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86/domain.c
>> @@ -426,8 +426,8 @@ static bool emulation_flags_ok(const struct domain *d,
>> uint32_t emflags)
>> return true;
>> }
>>
>>
flight 120340 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120340/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 8b13bca9b81490fc0e42df25d5feb82bbb47833e
baseline version:
ovmf
On Thu, Mar 08, 2018 at 12:52:31PM +, Igor Druzhinin wrote:
> This should help to avoid problems with accessing the device after
> migration/resume without PV drivers. Older systems will acquire
> the new record when migrated which should not change their state for
> worse.
>
> Signed-off-by:
On Fri, Mar 09, 2018 at 11:33:35AM +, Ian Jackson wrote:
> Eduardo Habkost writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict
> until just before os_setup_post"):
> > On Thu, Mar 08, 2018 at 05:39:09PM +, Ian Jackson wrote:
> > [...]
> > > diff --git a/vl.c b/vl.c
> > > +
In future patches, the structure will be extended with further information,
and this is far cleaner than adding extra parameters.
One minor tweak is that the setting of guest_type needs to be deferred until
config is known-good to dereference, but this doesn't result in any changed
behaviour as
The share_xen_page_with_guest() functions are used by common code, and are
implemented the same by each arch. Move the declarations into the common mm.h
rather than duplicating them in each arch/mm.h
Turn an int readonly into a boolean enum, to retain ro/rw context at the
callsites, but use
Neither domcr_flags nor config are used on either side. Drop them, making
{hvm,pv}_domain_initialise() symmetric with all the other domain/vcpu
initialise/destroy calls.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
flight 120305 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120305/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 7 xen-boot fail REGR. vs. 118324
We have a robot that is trying to send copies of the commits to
xen.git#staging (and I think also staging-NN) to the mailing list
xen-stag...@lists.xenproject.org.
That list was retired, apparently by mistake, in November[1]. But
no-one has complained.
We could reinstate the list, or shut down
On Fri, Mar 9, 2018 at 12:17 PM, awokd wrote:
> On Fri, March 9, 2018 12:04 pm, George Dunlap wrote:
>
>> I'm all for encouraging people to jump into Xen, but I agree with
>> Andre here, that you should really count the cost. I doubt this is
>> the sort of thing a single
On Fri, Mar 09, 2018 at 12:07:21PM +, Ian Jackson wrote:
> Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict until
> just before os_setup_post"):
> > Eduardo Habkost writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict
> > until just before os_setup_post"):
> > > I
The only relevent initialisation for the idle domain is the context switch and
poisoned pointers. Collect these bits together early in the function and exit
when complete (although as a consequence, the e820 and vtsc lock
initialisation are moved forwards). This allows us to remove subsequent
Hi Julien,
On Fri, Mar 09, 2018 at 10:22:09AM +, Julien Grall wrote:
>Hi Peng,
>
>On 09/03/18 09:05, Peng Fan wrote:
>>On Thu, Mar 08, 2018 at 03:13:50PM +, Julien Grall wrote:
>>>On 08/03/18 12:43, Peng Fan wrote:
>>>There are a major difference between Dom0 and DomU in your setup.
Currently with the native tool chain on Debian Jessie ./test_x86_emulator
yields:
Testing AVX2 256bit single native execution...okay
Testing AVX2 256bit single 64-bit code sequence...[line 933] failed!
The bug is that libc's memcpy() in read() uses %xmm8 (specifically, in
1 - 100 of 177 matches
Mail list logo