xend have been replaced by libxenlight (libxl) for many Xen releases
now.
Signed-off-by: Anthony PERARD
Acked-by: Stefano Stabellini
---
hw/xenpv/xen_machine_pv.c | 2 +-
include/hw/xen/xen.h | 2 +-
qemu-options.hx | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff
From: Paul Durrant
The new xen-block XenDevice implementation requires the same core
dataplane as the legacy xen_disk implementation it will eventually replace.
This patch therefore copies the legacy xen_disk.c source module into a new
dataplane/xen-block.c source module as the basis for the new
On 1/14/19 7:44 AM, Juergen Gross wrote:
> Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable'
> sched_clock() interface") broke Xen guest time handling across
> migration:
>
> [ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done.
> [ 187.251137] OOM ki
From: Paul Durrant
This patch adds a new source module, xen-bus-helper.c, which builds on
basic libxenstore primitives to provide functions to create (setting
permissions appropriately) and destroy xenstore areas, and functions to
'printf' and 'scanf' nodes therein. The main xen-bus code then use
From: Paul Durrant
This patch adds new XenDevice-s: 'xen-disk' and 'xen-cdrom', both derived
from a common 'xen-block' parent type. These will eventually replace the
'xen_disk' (note the underscore rather than hyphen) legacy PV backend but
it is illustrative to build up the implementation increme
From: Paul Durrant
The legacy PV backend infrastructure provides functions to bind, unbind
and send notifications to event channnels. Similar functionality will be
required by XenDevice implementations so this patch adds the necessary
support.
Signed-off-by: Paul Durrant
Reviewed-by: Anthony Pe
From: Paul Durrant
...and xen_backend.h to xen-legacy-backend.h
Rather than attempting to convert the existing backend infrastructure to
be QOM compliant (which would be hard to do in an incremental fashion),
subsequent patches will introduce a completely new framework for Xen PV
backends. Hence
From: Paul Durrant
This patch adds the basic boilerplate for a 'XenBus' object that will act
as a parent to 'XenDevice' PV backends.
A new 'XenBridge' object is also added to connect XenBus to the system bus.
The XenBus object is instantiated by a new xen_bus_init() function called
from the same
From: Peter Maydell
Coverity (CID 796599) points out that xen_pt_setup_vga() trusts
the rom->size field in the BIOS ROM from a PCI passthrough VGA
device, and uses it as an index into the memory which contains
the BIOS image. A corrupt BIOS ROM could therefore cause us to
index off the end of the
From: Zhao Yan
For some pci device, even its PCI_INTERRUPT_PIN is not 0, it actually
doesn't support INTx mode, so its machine irq read from host sysfs is 0.
In that case, report PCI_INTERRUPT_PIN as 0 to guest and let passthrough
continue.
Reviewed-by: Roger Pau Monné
Signed-off-by: Zhao Yan
From: Paul Durrant
The legacy PV backend infrastructure provides functions to map, unmap and
copy pages granted by frontends. Similar functionality will be required
by XenDevice implementations so this patch adds the necessary support.
Signed-off-by: Paul Durrant
Reviewed-by: Anthony Perard
Si
From: Paul Durrant
A Xen PV frontend communicates its state to the PV backend by writing to
the 'state' key in the frontend area in xenstore. It is therefore
necessary for a XenDevice implementation to be notified whenever the
value of this key changes.
This patch adds code to do this as follows
erard/qemu-dm.git
tags/pull-xen-20190114
for you to fetch changes up to c6025bd197d0dbcc5067553fd12538d8b29383c2:
xen-block: avoid repeated memory allocation (2019-01-14 13:45:40 +)
Xen queue
* Xen PV backend 'qdevificati
>>> On 07.01.19 at 08:42, wrote:
> Argo doesn't use compat hypercall or argument translation but can use some
> of the infrastructure for validating the hypercall argument structures to
> ensure that the struct sizes, offsets and compositions don't vary between 32
> and 64bit, so add that here in
>>> On 14.01.19 at 13:00, wrote:
> On 14/01/2019 11:39, Jan Beulich wrote:
>> First of all a PCLMULQDQ dependency was missing entirely. Add it as well
>> as AESNI and SHA to SSE2, as all of them act on vectors of integers,
>> whereas plain SSE supports vectors of single precision floats only. This
ping?
On 10/12/2018 10:03, Xin Li wrote:
> From: Talons Lee
>
> Commit e657fcc clears cpu capability bit instead of using fake cpuid
> value, the EXTD should always be off for PV guest without depending
> on cpuid value. So remove the cpuid check in xen_read_msr_safe() to
> always clear the X2AP
Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable'
sched_clock() interface") broke Xen guest time handling across
migration:
[ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 187.251137] OOM killer disabled.
[ 187.251137] Freezing remaining fre
On 11/01/2019 21:35, Boris Ostrovsky wrote:
> On 1/11/19 7:08 AM, Juergen Gross wrote:
>> @@ -421,6 +424,11 @@ void xen_restore_time_memory_area(void)
>> if (ret != 0)
>> pr_notice("Cannot restore secondary vcpu_time_info (err %d)",
>>ret);
>> +
>> +out:
>>
flight 131945 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131945/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops broken
build-i386
On Fri, Jan 11, 2019 at 06:16:45PM +, Peter Maydell wrote:
> On Fri, 11 Jan 2019 at 18:13, Anthony PERARD
> wrote:
> >
> > On Fri, Jan 11, 2019 at 06:09:41PM +, Anthony PERARD wrote:
> > > Patch "xen: add event channel interface for XenDevice-s" makes use of
> > > the type xenevtchn_port_
On 14/01/2019 11:39, Jan Beulich wrote:
> First of all a PCLMULQDQ dependency was missing entirely. Add it as well
> as AESNI and SHA to SSE2, as all of them act on vectors of integers,
> whereas plain SSE supports vectors of single precision floats only. This
> is in line with how e.g. binutils an
Am Mon, 14 Jan 2019 11:28:57 +
schrieb Wei Liu :
> Are you saying that the breakage is shown when you put a snapshot of
> ovmf under xen.git? How does ovmf distribute their snapshot? How is that
> generated? Does it contain snapshots of submodules it needs already?
I export all required sourc
First of all a PCLMULQDQ dependency was missing entirely. Add it as well
as AESNI and SHA to SSE2, as all of them act on vectors of integers,
whereas plain SSE supports vectors of single precision floats only. This
is in line with how e.g. binutils and gcc treat them.
Signed-off-by: Jan Beulich
-
For VPSADBW this likely was a result of bad copy-and-paste.
For VPS{L,R}LDQ comment and code were not in line, but then again the
comment also wasn't fully updated from the AVX2 original it got cloned
from.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/x86_emulate/x86_emulate.c
+++ b/xen/arch/x
On Mon, Jan 14, 2019 at 02:47:58AM -0700, Jan Beulich wrote:
> >>> On 11.01.19 at 20:23, wrote:
> > CLONE_NEWIPC was introduced in Linux 2.6.19, on the 29th of November
> > 2006, which was 12 years, 1 month, and 14 days ago.
>
> Thanks for the very precise counting, the latter part which will be
>>> On 14.01.19 at 12:05, wrote:
> On 04/01/2019 14:04, Jan Beulich wrote:
>>> dom0 (either PV, or PVH) cannot use the HPET
>>> safely, even if it is restricted to just read-only access. Dom0 must
>>> under no circumstance interact directly with the hardware HPET, as it is
>>> a direct interrupt
On Mon, Jan 14, 2019 at 9:32 AM Christopher Clark
wrote:
>
> On Fri, Jan 11, 2019 at 1:27 AM Roger Pau Monné wrote:
> > On Fri, Jan 11, 2019 at 7:04 AM Christopher Clark
> > wrote:
> > >
> > > On Thu, Jan 10, 2019 at 2:19 AM Roger Pau Monné
> > > wrote:
> > > >
> > > > On Mon, Jan 7, 2019 at
On Sun, Jan 13, 2019 at 09:17:44PM +0100, Olaf Hering wrote:
> On Wed, Nov 28, Wei Liu wrote:
>
> > OVMF has become dependent on OpenSSL, which it is included as a submodule.
> > Initialise submodules before building.
>
> > +++ b/tools/firmware/ovmf-makefile
> > build:
> > + $(GIT) submodule u
On 04/01/2019 14:04, Jan Beulich wrote:
>> dom0 (either PV, or PVH) cannot use the HPET
>> safely, even if it is restricted to just read-only access. Dom0 must
>> under no circumstance interact directly with the hardware HPET, as it is
>> a direct interrupt source.
> But reads don't cause interru
On 1/14/19 11:53 AM, Jan Beulich wrote:
On 14.01.19 at 10:34, wrote:
On 1/12/19 12:04 AM, Boris Ostrovsky wrote:
On 12/14/18 6:49 AM, Razvan Cojocaru wrote:
Block interrupts (in vmx_intr_assist()) for the duration of
processing a sync vm_event (similarly to the strategy
currently used for sin
On 14/01/2019 10:13, Juergen Gross wrote:
> I have started to include the version number of series associated to each
> feature. Can each owner send an update on the version number if the series
> was posted upstream?
>
> = Projects =
>
> == Hypervisor ==
>
> * Improvements to domain creation (v2
flight 131942 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131942/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win10-i386 broken
test-amd64-amd64-xl-qcow2
Hi,
On 14/01/2019 09:34, Razvan Cojocaru wrote:
On 1/12/19 12:04 AM, Boris Ostrovsky wrote:
On 12/14/18 6:49 AM, Razvan Cojocaru wrote:
Block interrupts (in vmx_intr_assist()) for the duration of
processing a sync vm_event (similarly to the strategy
currently used for single-stepping). Otherwi
Hey there!
I'm going to extend openOCD. There is a new lightwight TAP AHB-Controller
(AHBL) from Hilscher Companny. Depending on the chip thre is a ARM9 (netX50), a
RISCV(netIOL), or … below it.
I'm going to add support to openOCD for this TAP-Device. I’m new to openOCD
codebase.
I was look
On 1/7/19 7:37 PM, Souptick Joarder wrote:
Remove duplicate header which is included twice.
Signed-off-by: Souptick Joarder
Reviewed-by: Oleksandr Andrushchenko
---
arch/arm/xen/mm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/xen/mm.c b/arch/arm/xen/mm.c
index cb44aa2..e1
>>> On 14.01.19 at 04:45, wrote:
> So let's keep the linker-accessible variable as a type that works for the
> linker (which really could be anything as long as you use the address, not
> the value), but name it something else - a name that screams "DON'T USE ME
> UNLESS YOU KNOW WHAT YOU'RE DOING
This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.12 so that people have an idea what is going on and
prioritise accordingly.
You're welcome to provide description and use cases of the feature you're
working on.
= Timeline =
We now adopt a fixed
>>> On 11.01.19 at 19:04, wrote:
> On Fri, 11 Jan 2019, Jan Beulich wrote:
>> >>> On 11.01.19 at 03:14, wrote:
>> > Hi Juergen, Jan,
>> >
>> > I spoke with Julien: we are both convinced that the unsigned long
>> > solution is best. But Julien also did some research and he thinks that
>> > Jan's
>>> On 14.01.19 at 10:34, wrote:
> On 1/12/19 12:04 AM, Boris Ostrovsky wrote:
>> On 12/14/18 6:49 AM, Razvan Cojocaru wrote:
>>> Block interrupts (in vmx_intr_assist()) for the duration of
>>> processing a sync vm_event (similarly to the strategy
>>> currently used for single-stepping). Otherwise
>>> On 11.01.19 at 20:23, wrote:
> CLONE_NEWIPC was introduced in Linux 2.6.19, on the 29th of November
> 2006, which was 12 years, 1 month, and 14 days ago.
Thanks for the very precise counting, the latter part which will be
wrong - even if just slightly - by the time you commit it ;-)
> Nevert
On 1/14/19 10:23 AM, Oleksandr Andrushchenko wrote:
> Hello, Hans!
> Could you please take a look at my answers below and kindly let me know
> if we are ready for (final?) v4 from your point of view.
Looks good, so I'm looking forward to a v4.
Regards,
Hans
>
> Konrad, Xen-devel - do y
On 1/12/19 12:04 AM, Boris Ostrovsky wrote:
On 12/14/18 6:49 AM, Razvan Cojocaru wrote:
Block interrupts (in vmx_intr_assist()) for the duration of
processing a sync vm_event (similarly to the strategy
currently used for single-stepping). Otherwise, attempting
to emulate an instruction when requ
On 02.01.19 19:15, Andrew Cooper wrote:
On 02/01/2019 16:56, Olaf Hering wrote:
On Mon, Dec 31, Andrew Cooper wrote:
* tbuf_size and tevt_mask
Given that xentrace can set them at runtime, and it is debugging
functionality, I don't see a plausible use the command line options at all.
'tbuf_si
Hello, Hans!
Could you please take a look at my answers below and kindly let me know
if we are ready for (final?) v4 from your point of view.
Konrad, Xen-devel - do you have any objections/comments on this?
Thank you,
Oleksandr
On 12/17/18 9:37 AM, Oleksandr Andrushchenko wrote:
Hello, Hans!
>>> On 11.01.19 at 17:58, wrote:
> On Fri, 11 Jan 2019, Jan Beulich wrote:
>> >> > --- a/xen/arch/arm/setup.c
>> >> > +++ b/xen/arch/arm/setup.c
>> >> > @@ -772,8 +772,10 @@ void __init start_xen(unsigned long
>> >> > boot_phys_offset,
>> >> >
>> >> > /* Register Xen's load address as a bo
Hello Jairo,
I was on vacations last week, and a regular CES rush the week before.
Please give me some time to sort out what else has happened during that period,
and I'll get back to you.
--
Sincerely,
Andrii Anisov.
___
Xen-devel mailing list
Xen-d
On Fri, Jan 11, 2019 at 3:54 AM Jan Beulich wrote:
>
> >>> On 07.01.19 at 08:42, wrote:
> > --- a/xen/common/argo.c
> > +++ b/xen/common/argo.c
> > @@ -17,7 +17,177 @@
> > */
> >
> > #include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > #include
> > +#inclu
On Fri, Jan 11, 2019 at 1:27 AM Roger Pau Monné wrote:
> On Fri, Jan 11, 2019 at 7:04 AM Christopher Clark
> wrote:
> >
> > On Thu, Jan 10, 2019 at 2:19 AM Roger Pau Monné wrote:
> > >
> > > On Mon, Jan 7, 2019 at 8:44 AM Christopher Clark
> > > wrote:
> > > > +/*
> > > > + * Locking is organi
On 12/01/2019 10:07, Lukas Bulwahn wrote:
> In the linux kernel MAINTAINERS file, largely
> "xen-devel@lists.xenproject.org (moderated for non-subscribers)"
> is used to refer to the xen-devel mailing list.
>
> The DRM DRIVERS FOR XEN section entry mentions
> xen-de...@lists.xen.org instead, but
101 - 149 of 149 matches
Mail list logo
