On 24/04/18 20:51, Andrew Cooper wrote:
> By default, the SYSCALL MSRs are not intercepted, and accesses are completed
> by hardware. The SYSENTER MSRs are intercepted for cross-vendor
> purposes (albeit needlessly in the common case), and are fully emulated.
>
> However, {RD,WR}MSR instructions
On 24.04.2018 19:58, Ian Jackson wrote:
> I'm going to be editing this function and it makes sense to clean up
> this style problem in advance.
>
> Signed-off-by: Ian Jackson
> CC: Paolo Bonzini
> CC: Markus Armbruster
> CC:
On 24.04.2018 19:58, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
> CC: Paolo Bonzini
> CC: Markus Armbruster
> CC: Daniel P. Berrange
> CC: Michael Tokarev
> Reviewed-by: Philippe
On 24.04.2018 19:58, Ian Jackson wrote:
> This makes it much easier to find a particular thing in config.log.
>
> We have to use the ${BASH_LINENO[*]} syntax which is a syntax error in
> other shells, so test what shell we are running and use eval.
>
> The extra output is only printed if
flight 122363 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122363/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 16 guest-localmigrate/x10 fail REGR. vs.
122343
On 04/24/2018 02:51 PM, Andrew Cooper wrote:
> By default, the SYSCALL MSRs are not intercepted, and accesses are completed
> by hardware. The SYSENTER MSRs are intercepted for cross-vendor
> purposes (albeit needlessly in the common case), and are fully emulated.
>
> However, {RD,WR}MSR
On Tue, Apr 24, 2018 at 10:58 AM, Ian Jackson wrote:
> perror() is defined to fprintf(stderr,...). HACKING says
> fprintf(stderr,...) is wrong. So perror() is too.
>
> Signed-off-by: Ian Jackson
> CC: Paolo Bonzini
>
Had a meeting with Daniel and talked about bringing out generic
part of hyper-dmabuf to the userspace, which means we most likely
reuse IOCTLs defined in xen-zcopy for our use-case if we follow
his suggestion.
So assuming we use these IOCTLs as they are,
Several things I would like you to
This run is configured for baseline tests only.
flight 74639 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74639/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf ee4dc24f57c32a445e7c747396c9bfbd8b221568
baseline
flight 122360 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122360/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win10-i386 broken
This run is configured for baseline tests only.
flight 74638 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74638/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail
On 24 April 2018 at 18:58, Ian Jackson wrote:
> I'm going to be editing this function and it makes sense to clean up
> this style problem in advance.
>
> Signed-off-by: Ian Jackson
> CC: Paolo Bonzini
> CC: Markus
By default, the SYSCALL MSRs are not intercepted, and accesses are completed
by hardware. The SYSENTER MSRs are intercepted for cross-vendor
purposes (albeit needlessly in the common case), and are fully emulated.
However, {RD,WR}MSR instructions which happen to be emulated (FEP,
introspection,
flight 122362 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122362/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf ee4dc24f57c32a445e7c747396c9bfbd8b221568
baseline version:
ovmf
From: Ross Lagerwall
Xen unstable (to be in 4.11) has two new dmops, relocate_memory and
pin_memory_cacheattr. Use these to set up the VGA memory, replacing the
previous calls to libxc. This allows the VGA console to work properly
when QEMU is running restricted
We are going to want to use the dummy xendevicemodel_handle type in
new stub functions in the CONFIG_XEN_CTRL_INTERFACE_VERSION < 41000
section. So we need to provide that definition, or (as applicable)
include the appropriate header, earlier in the file.
(Ideally the newer compatibility layers
We need to restrict *all* the control fds that qemu opens. Looking in
/proc/PID/fd shows there are many; their allocation seems scattered
throughout Xen support code in qemu.
We must postpone the restrict call until roughly the same time as qemu
changes its uid, chroots (if applicable), and so
We are going to want to reuse this.
No functional change.
Signed-off-by: Ian Jackson
Reviewed-by: Anthony PERARD
Acked-by: Stefano Stabellini
---
hw/i386/xen/xen-hvm.c | 5 +++--
1 file changed, 3 insertions(+), 2
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC: Michael Tokarev
Reviewed-by: Philippe Mathieu-Daudé
---
v8: Remove one
And insist that it works.
Drop individual use of xendevicemodel_restrict and
xenforeignmemory_restrict. These are not actually effective in this
version of qemu, because qemu has a large number of fds open onto
various Xen control devices.
The restriction arrangements are still not right,
This series provides necessary support for running qemu as a Xen
device model without power equivalent to root. In particular, it
makes -xen-domid-restrict effective.
Compared to v8, it addresses review comments.
01/16 checkpatch: Add xendevicemodel_handle to the list of
r 02/16
perror() is defined to fprintf(stderr,...). HACKING says
fprintf(stderr,...) is wrong. So perror() is too.
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC:
From: Anthony PERARD
Xen libraries in 4.10 include a new xentoolcore library. This
contains the xentoolcore_restrict_all function which we are about to
want to use.
Signed-off-by: Ian Jackson
Acked-by: Stefano Stabellini
This is called just before os_setup_post. Currently none of the
accelerators provide this hook, but the Xen one is going to provide
one in a moment.
Signed-off-by: Ian Jackson
Reviewed-by: Eduardo Habkost
---
v7: New patch in this version of the
This allows the caller to specify a uid and gid to use, even if there
is no corresponding password entry. This will be useful in certain
Xen configurations.
We don't support just -runas because: (i) deprivileging without
calling setgroups would be ineffective (ii) given only a uid we don't
know
From: Ross Lagerwall
Saving the current state to xenstore may fail when running restricted
(in particular, after a migration). Therefore, don't report the error or
exit when running restricted. Toolstacks that want to allow running
QEMU restricted should instead make
This avoids checkpatch misparsing (as statements) long function
definitions or declarations, which sometimes start with constructs
like this:
static inline int xendevicemodel_relocate_memory(
xendevicemodel_handle *dmod, domid_t domid, ...
The type xendevicemodel_handle does not conform
This makes it much easier to find a particular thing in config.log.
We have to use the ${BASH_LINENO[*]} syntax which is a syntax error in
other shells, so test what shell we are running and use eval.
The extra output is only printed if configure is run with bash. On
systems where /bin/sh is
xc_interface_open etc. is not going to work if we have dropped
privilege, but xendevicemodel_shutdown will if everything is new
enough.
xendevicemodel_shutdown is only availabe in Xen 4.10 and later, so
provide a stub for earlier versions.
Signed-off-by: Ian Jackson
The last user was just removed; remove this function, accordingly.
Signed-off-by: Ian Jackson
Acked-by: Anthony PERARD
---
include/hw/xen/xen_common.h | 22 --
1 file changed, 22 deletions(-)
diff --git
I'm going to be editing this function and it makes sense to clean up
this style problem in advance.
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC: Michael
flight 122361 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122361/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf c3a84a8f7cedd97b34139cb6abde62f17b9d2b1c
baseline version:
xtf
Hi Julien,
Thank you for the feedback, we have a v3 agreement.
On Tue, Apr 24, 2018 at 6:12 PM, Julien Grall wrote:
> Hi Mirela,
>
>
> On 04/24/2018 12:02 PM, Mirela Simonovic wrote:
>>
>> Hi Julien,
>>
>> On Mon, Apr 23, 2018 at 1:15 PM, Julien Grall
Hello,
I tested xen 4.11.0 rc1 with NetBSD as dom0.
I could boot a NetBSD PV domU without problem, but at shutdown time (poweroff
in the domU), I got a Xen panic:
(XEN) Assertion 'cpu < nr_cpu_ids' failed at
...1/work/xen-4.11.0-rc1/xen/include/xen/cpumask.h:97
A xl destroy instead of poweroff
flight 122358 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122358/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 10 debian-install fail REGR. vs. 118324
On 04/24/2018 03:50 PM, Mirela Simonovic wrote:
Hi Julien,
Hi Mirela,
Thanks for the feedback.
On Mon, Apr 23, 2018 at 1:28 PM, Julien Grall wrote:
Hi Mirela,
On 20/04/18 13:25, Mirela Simonovic wrote:
In existing code the paging for non-boot CPUs is setup only
On 04/24/2018 06:02 PM, Takashi Iwai wrote:
On Tue, 24 Apr 2018 16:58:43 +0200,
Oleksandr Andrushchenko wrote:
On 04/24/2018 05:35 PM, Takashi Iwai wrote:
On Tue, 24 Apr 2018 16:29:15 +0200,
Oleksandr Andrushchenko wrote:
On 04/24/2018 05:20 PM, Takashi Iwai wrote:
On Mon, 16 Apr 2018
Hi,
On 04/24/2018 03:18 PM, Andrii Anisov wrote:
Can you quantify what would be the cost of keeping that code around
for IOMMU-less platform?
I'm not sure I understand your question. Do you mean a number of loc of
the passthrough feature for arm?
I meant that disabling something in Xen
Philippe Mathieu-Daudé writes:
> On 04/19/2018 01:45 PM, Ian Jackson wrote:
>> perror() is defined to fprintf(stderr,...). HACKING says
>> fprintf(stderr,...) is wrong. So perror() is too.
>>
>> Signed-off-by: Ian Jackson
>> CC: Paolo Bonzini
On Tue, Apr 24, 2018 at 04:56:23PM +0100, Lars Kurth wrote:
> This was discussed in an IRC discussion post the April x86 meeting.
>
> Signed-off-by: Lars Kurth
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
>
Hi Mirela,
On 04/24/2018 12:02 PM, Mirela Simonovic wrote:
Hi Julien,
On Mon, Apr 23, 2018 at 1:15 PM, Julien Grall wrote:
Hi Mirela,
On 20/04/18 13:25, Mirela Simonovic wrote:
Guests attempt to write into these registers on resume (for example
Linux).
Without this
This was discussed in an IRC discussion post the April x86 meeting.
Signed-off-by: Lars Kurth
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cc1fdc013f..fab76b0af4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -144,12
This follows up from a conversation after the April x86 community call, in
which I had
the following action: Lars to propose fixing CC issue in xen.git:MAINTAINERS
copying
the R section entries from Linux.git:MAINTAINERS (will need changes to
get_maintainers.pl also)
Lars Kurth (2):
Add
The syntax has been copied from the Linux Maintainers file. I moved the
following Linux
get_maintainer.pl patches to Xen, fixing up some merge issues (and a bug).
The get_maintainer.pl changes were based on the following git commits
*
On Tue, Apr 24, 2018 at 10:43:09AM -0500, Eric Blake wrote:
> On 04/24/2018 10:40 AM, Eric Blake wrote:
> > On 04/24/2018 10:18 AM, Daniel P. Berrangé wrote:
> >
> >>> - static void vreport(report_type type, const char *fmt, va_list ap)
> >>> + static void vreport(report_type type, int
On 04/24/2018 10:40 AM, Eric Blake wrote:
> On 04/24/2018 10:18 AM, Daniel P. Berrangé wrote:
>
>>> - static void vreport(report_type type, const char *fmt, va_list ap)
>>> + static void vreport(report_type type, int errnoval, const char *fmt,
>>> va_list ap)
>>> ...
>>> + if (errnoval >=
On 04/24/2018 10:18 AM, Daniel P. Berrangé wrote:
>> - static void vreport(report_type type, const char *fmt, va_list ap)
>> + static void vreport(report_type type, int errnoval, const char *fmt,
>> va_list ap)
>> ...
>> + if (errnoval >= 0) {
>> + error_printf(": %s",
On Tue, Apr 24, 2018 at 03:53:48PM +0100, Ian Jackson wrote:
> Philippe Mathieu-Daudé writes ("Re: [Qemu-devel] [PATCH 15/16] os-posix:
> cleanup: Replace perror with error_report"):
> > On 04/19/2018 01:45 PM, Ian Jackson wrote:
> > > -perror("mlockall");
> > > +
Anthony PERARD writes ("Re: [PATCH 05/16] xen: defer call to xen_restrict until
just before os_setup_post"):
> I think this include is not needed anymore, and can go away from the
> patch series.
Yes.
Thanks,
Ian.
___
Xen-devel mailing list
Eric Blake writes ("Re: [Qemu-devel] [PATCH 16/16] configure: do_compiler: Dump
some extra info under bash"):
> That's still fork-heavy. You could do:
>
> test -n "$BASH_VERSION" && eval '
> echo >>config.log "
> funcs: ${FUNCNAME[*]}
> lines: ${BASH_LINENO[*]}
> files: ${BASH_SOURCE[*]}"'
>
>
On Tue, 24 Apr 2018 16:58:43 +0200,
Oleksandr Andrushchenko wrote:
>
> On 04/24/2018 05:35 PM, Takashi Iwai wrote:
> > On Tue, 24 Apr 2018 16:29:15 +0200,
> > Oleksandr Andrushchenko wrote:
> >> On 04/24/2018 05:20 PM, Takashi Iwai wrote:
> >>> On Mon, 16 Apr 2018 08:24:51 +0200,
> >>> Oleksandr
On 04/24/2018 05:35 PM, Takashi Iwai wrote:
On Tue, 24 Apr 2018 16:29:15 +0200,
Oleksandr Andrushchenko wrote:
On 04/24/2018 05:20 PM, Takashi Iwai wrote:
On Mon, 16 Apr 2018 08:24:51 +0200,
Oleksandr Andrushchenko wrote:
+static irqreturn_t evtchnl_interrupt_req(int irq, void *dev_id)
+{
+
Philippe Mathieu-Daudé writes ("Re: [Qemu-devel] [PATCH 15/16] os-posix:
cleanup: Replace perror with error_report"):
> On 04/19/2018 01:45 PM, Ian Jackson wrote:
> > -perror("mlockall");
> > +error_report("mlockall: %s", strerror(errno));
> > }
> >
> > return ret;
>
Hi Julien,
Thanks for the feedback.
On Mon, Apr 23, 2018 at 1:28 PM, Julien Grall wrote:
> Hi Mirela,
>
>
> On 20/04/18 13:25, Mirela Simonovic wrote:
>>
>> In existing code the paging for non-boot CPUs is setup only on boot. The
>> setup is triggered from start_xen()
flight 122392 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122392/
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 Tue, 24 Apr 2018 16:29:15 +0200,
Oleksandr Andrushchenko wrote:
>
> On 04/24/2018 05:20 PM, Takashi Iwai wrote:
> > On Mon, 16 Apr 2018 08:24:51 +0200,
> > Oleksandr Andrushchenko wrote:
> >> +static irqreturn_t evtchnl_interrupt_req(int irq, void *dev_id)
> >> +{
> >> + struct
On 04/24/2018 05:20 PM, Takashi Iwai wrote:
On Mon, 16 Apr 2018 08:24:51 +0200,
Oleksandr Andrushchenko wrote:
+static irqreturn_t evtchnl_interrupt_req(int irq, void *dev_id)
+{
+ struct xen_snd_front_evtchnl *channel = dev_id;
+ struct xen_snd_front_info *front_info =
Anthony PERARD writes ("Re: [PATCH 03/16] xen: link against xentoolcore"):
> On Thu, Apr 19, 2018 at 05:45:06PM +0100, Ian Jackson wrote:
> > xen_pc="xencontrol xenstore xenguest xenforeignmemory xengnttab"
> > -xen_pc="$xen_pc xenevtchn xendevicemodel"
> > +xen_pc="$xen_pc xenevtchn
On Mon, 16 Apr 2018 08:24:51 +0200,
Oleksandr Andrushchenko wrote:
> +static irqreturn_t evtchnl_interrupt_req(int irq, void *dev_id)
> +{
> + struct xen_snd_front_evtchnl *channel = dev_id;
> + struct xen_snd_front_info *front_info = channel->front_info;
> + struct xensnd_resp *resp;
Can you quantify what would be the cost of keeping that code around
for IOMMU-less platform?
I'm not sure I understand your question. Do you mean a number of loc of
the passthrough feature for arm?
--
*Andrii Anisov*
___
Xen-devel mailing list
On 04/24/2018 04:55 PM, Takashi Iwai wrote:
On Mon, 16 Apr 2018 08:24:49 +0200,
Oleksandr Andrushchenko wrote:
--- /dev/null
+++ b/sound/xen/Kconfig
@@ -0,0 +1,10 @@
+# ALSA Xen drivers
+
+config SND_XEN_FRONTEND
+ tristate "Xen para-virtualized sound frontend driver"
+ depends on
On Mon, 16 Apr 2018 08:24:49 +0200,
Oleksandr Andrushchenko wrote:
> --- /dev/null
> +++ b/sound/xen/Kconfig
> @@ -0,0 +1,10 @@
> +# ALSA Xen drivers
> +
> +config SND_XEN_FRONTEND
> + tristate "Xen para-virtualized sound frontend driver"
> + depends on XEN && SND_PCM
Please do select
On 24/04/18 14:35, Konrad Rzeszutek Wilk wrote:
> On April 24, 2018 5:44:33 AM EDT, Andrew Cooper
> wrote:
>> Signed-off-by: Andrew Cooper
>> ---
>> CC: Jan Beulich
>> CC: Juergen Gross
>
> You are
On April 24, 2018 5:44:33 AM EDT, Andrew Cooper
wrote:
>Signed-off-by: Andrew Cooper
>---
>CC: Jan Beulich
>CC: Juergen Gross
You are missing an Reported-by..
Also pls
Reviewed-by: Konrad Rzeszutek
On Tuesday 24 April 2018 04:33 PM, Dario Faggioli wrote:
On Tue, 2018-04-24 at 14:30 +0530, Praveen Kumar wrote:
Hi Dario,
Hi!
On Tuesday 17 April 2018 04:16 PM, Dario Faggioli wrote:
On Tue, 2018-04-03 at 22:25 +0530, Praveen Kumar wrote:
+if ( svc->credit < entry->credit )
+
On Tue, Apr 24, 2018 at 03:18:14PM +0200, Luc Van Oostenryck wrote:
> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
> which is a typedef for an enum type, but the implementation in this
> driver returns an 'int'.
>
> Fix this by returning 'netdev_tx_t' in this driver too.
On Tue, Apr 24, 2018 at 03:18:12PM +0200, Luc Van Oostenryck wrote:
> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
> which is a typedef for an enum type, but the implementation in this
> driver returns an 'int'.
>
> Fix this by returning 'netdev_tx_t' in this driver too.
The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
which is a typedef for an enum type, but the implementation in this
driver returns an 'int'.
Fix this by returning 'netdev_tx_t' in this driver too.
Signed-off-by: Luc Van Oostenryck
---
The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
which is a typedef for an enum type, but the implementation in this
driver returns an 'int'.
Fix this by returning 'netdev_tx_t' in this driver too.
Signed-off-by: Luc Van Oostenryck
---
Signed-off-by: Ian Jackson
---
cr-for-branches | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cr-for-branches b/cr-for-branches
index cf48390..c4de52f 100755
--- a/cr-for-branches
+++ b/cr-for-branches
@@ -31,7 +31,7 @@ scriptoptions="$1"; shift
On 04/24/2018 02:54 PM, Daniel Vetter wrote:
On Mon, Apr 23, 2018 at 03:10:35PM +0300, Oleksandr Andrushchenko wrote:
On 04/23/2018 02:52 PM, Wei Liu wrote:
On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote:
the gntdev.
I think this is generic enough that it could
On Mon, Apr 23, 2018 at 03:10:35PM +0300, Oleksandr Andrushchenko wrote:
> On 04/23/2018 02:52 PM, Wei Liu wrote:
> > On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote:
> > > > > the gntdev.
> > > > >
> > > > > I think this is generic enough that it could be implemented
>>> On 24.04.18 at 11:44, wrote:
> Signed-off-by: Andrew Cooper
Acked-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
>>> On 24.04.18 at 12:13, wrote:
> On Tue, Apr 24, 2018 at 10:46:38AM +0100, George Dunlap wrote:
>> On Mon, Apr 23, 2018 at 11:33 AM, Jan Beulich wrote:
>> On 23.04.18 at 12:25, wrote:
>> >> On Mon, Apr 23, 2018 at
On 24/04/18 12:31, Tim Deegan wrote:
> At 07:45 +0200 on 23 Apr (1524469545), Juergen Gross wrote:
>> On 22/04/18 18:39, Tim Deegan wrote:
>>> At 19:11 +0200 on 21 Apr (1524337893), Juergen Gross wrote:
On 21/04/18 15:32, Tim Deegan wrote:
> At 09:44 +0200 on 19 Apr (1524131080), Juergen
flight 122357 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122357/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 122212
test-armhf-armhf-libvirt 14
On 24/04/2018 12:04, Andrii Anisov wrote:
Hello Julien,
On 24.04.18 13:06, Julien Grall wrote:
I believe that passthrough should be kept as core Xen, it is small and
quite tight to the rest of Xen.
It might be.
But I would be interested to know what would be the rationale to
disable
> While testing MSR vm_events, we've come accross some puzzling behaviour
> while trying to follow the guest's MSR_LSTAR: it starts out as zero,
> then it changes value before the first MSR write event, without going
> through svm_msr_write_intercept(). The culprit seems to be a
> svm_vmsave_pa()
On Tue, 2018-04-24 at 14:30 +0530, Praveen Kumar wrote:
> Hi Dario,
>
Hi!
> On Tuesday 17 April 2018 04:16 PM, Dario Faggioli wrote:
> > On Tue, 2018-04-03 at 22:25 +0530, Praveen Kumar wrote:
> > >
> > > +if ( svc->credit < entry->credit )
> > > +node = >rb_left;
> > > +
Hello Julien,
On 24.04.18 13:06, Julien Grall wrote:
I believe that passthrough should be kept as core Xen, it is small and
quite tight to the rest of Xen.
It might be.
But I would be interested to know what would be the rationale to
disable that. Do you foresee certification on IOMMU-less
Hi Julien,
On Mon, Apr 23, 2018 at 1:15 PM, Julien Grall wrote:
> Hi Mirela,
>
>
> On 20/04/18 13:25, Mirela Simonovic wrote:
>>
>> Guests attempt to write into these registers on resume (for example
>> Linux).
>> Without this patch a data abort exception will be raised to
flight 74637 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74637/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-i386-daily-netboot-pvgrub 10 debian-di-install fail like 74630
At 07:45 +0200 on 23 Apr (1524469545), Juergen Gross wrote:
> On 22/04/18 18:39, Tim Deegan wrote:
> > At 19:11 +0200 on 21 Apr (1524337893), Juergen Gross wrote:
> >> On 21/04/18 15:32, Tim Deegan wrote:
> >>> At 09:44 +0200 on 19 Apr (1524131080), Juergen Gross wrote:
> Another alternative
On 24/04/18 12:14, Oleksandr Andrushchenko wrote:
> On 04/24/2018 01:01 PM, Wei Liu wrote:
>> On Tue, Apr 24, 2018 at 11:08:41AM +0200, Juergen Gross wrote:
>>> On 24/04/18 11:03, Oleksandr Andrushchenko wrote:
On 04/24/2018 11:40 AM, Juergen Gross wrote:
> On 24/04/18 10:07, Oleksandr
On 04/24/2018 01:01 PM, Wei Liu wrote:
On Tue, Apr 24, 2018 at 11:08:41AM +0200, Juergen Gross wrote:
On 24/04/18 11:03, Oleksandr Andrushchenko wrote:
On 04/24/2018 11:40 AM, Juergen Gross wrote:
On 24/04/18 10:07, Oleksandr Andrushchenko wrote:
On 04/24/2018 10:51 AM, Juergen Gross wrote:
On Tue, Apr 24, 2018 at 10:46:38AM +0100, George Dunlap wrote:
> On Mon, Apr 23, 2018 at 11:33 AM, Jan Beulich wrote:
> On 23.04.18 at 12:25, wrote:
> >> On Mon, Apr 23, 2018 at 12:55:45AM -0600, Jan Beulich wrote:
> >>> >>> On 20.04.18 at 21:12,
On 04/24/2018 10:52 AM, Andrii Anisov wrote:
Hello Julien,
Hi Andrii,
On 24.04.18 12:01, Julien Grall wrote:
You can't unselect HAS_PASSTHROUGH support. Given that you are going
to have passthrough in the future, I don't much see the point to try
to allow that option to be disabled.
If
Hello,
While testing MSR vm_events, we've come accross some puzzling behaviour
while trying to follow the guest's MSR_LSTAR: it starts out as zero,
then it changes value before the first MSR write event, without going
through svm_msr_write_intercept(). The culprit seems to be a
svm_vmsave_pa()
On Tue, Apr 24, 2018 at 11:08:41AM +0200, Juergen Gross wrote:
> On 24/04/18 11:03, Oleksandr Andrushchenko wrote:
> > On 04/24/2018 11:40 AM, Juergen Gross wrote:
> >> On 24/04/18 10:07, Oleksandr Andrushchenko wrote:
> >>> On 04/24/2018 10:51 AM, Juergen Gross wrote:
> On 24/04/18 07:43,
Hello Julien,
On 24.04.18 12:01, Julien Grall wrote:
You can't unselect HAS_PASSTHROUGH support. Given that you are going
to have passthrough in the future, I don't much see the point to try
to allow that option to be disabled.
If we are speaking of R-Car Gen3, you might be right. We are
On 24/04/18 11:44, Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper
Release-acked-by: Juergen Gross
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
On Mon, Apr 23, 2018 at 11:33 AM, Jan Beulich wrote:
On 23.04.18 at 12:25, wrote:
>> On Mon, Apr 23, 2018 at 12:55:45AM -0600, Jan Beulich wrote:
>>> >>> On 20.04.18 at 21:12, wrote:
>>> > Two options for signature
On Mon, Apr 16, 2018 at 06:32:24PM +0100, Anthony PERARD wrote:
> In case QEMU have restricted access to the system, open the file for it,
> and QEMU will save its state to this file descritor.
>
> Signed-off-by: Anthony PERARD
Acked-by: Wei Liu
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Juergen Gross
---
xen/arch/x86/spec_ctrl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/spec_ctrl.c b/xen/arch/x86/spec_ctrl.c
index
flight 122356 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122356/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-win7-amd64 7 xen-boot fail REGR. vs. 122255
On Mon, Apr 23, 2018 at 04:45:28PM +0100, Anthony PERARD wrote:
> On Mon, Apr 23, 2018 at 10:20:42AM +0100, Wei Liu wrote:
> > On Mon, Apr 16, 2018 at 06:32:24PM +0100, Anthony PERARD wrote:
> > > In case QEMU have restricted access to the system, open the file for it,
> > > and QEMU will save its
On 04/24/2018 12:08 PM, Juergen Gross wrote:
On 24/04/18 11:03, Oleksandr Andrushchenko wrote:
On 04/24/2018 11:40 AM, Juergen Gross wrote:
On 24/04/18 10:07, Oleksandr Andrushchenko wrote:
On 04/24/2018 10:51 AM, Juergen Gross wrote:
On 24/04/18 07:43, Oleksandr Andrushchenko wrote:
On
On 24/04/18 11:03, Oleksandr Andrushchenko wrote:
> On 04/24/2018 11:40 AM, Juergen Gross wrote:
>> On 24/04/18 10:07, Oleksandr Andrushchenko wrote:
>>> On 04/24/2018 10:51 AM, Juergen Gross wrote:
On 24/04/18 07:43, Oleksandr Andrushchenko wrote:
> On 04/24/2018 01:41 AM, Boris
Hi,
On 04/23/2018 04:34 PM, Jan Beulich wrote:
On 21.02.18 at 22:46, wrote:
Move the functions that reference x86 hvm data structures to its own
file. Rename pci_clean_dpci_irqs to arch_pci_clean_irqs.
There is still one location in that file which references
On 04/24/2018 11:40 AM, Juergen Gross wrote:
On 24/04/18 10:07, Oleksandr Andrushchenko wrote:
On 04/24/2018 10:51 AM, Juergen Gross wrote:
On 24/04/18 07:43, Oleksandr Andrushchenko wrote:
On 04/24/2018 01:41 AM, Boris Ostrovsky wrote:
On 04/23/2018 08:10 AM, Oleksandr Andrushchenko wrote:
1 - 100 of 122 matches
Mail list logo