>>> On 10.04.17 at 18:46, wrote:
> I have a (I think) less intrusive fix, which relies on using _Pragma, pasted
> below. Let me know what you think, and I can formally submit it.
Personally I like this much better as a workaround, provided the
omitted warning isn't just cosmetic (i.e. the generat
On 03/29/2017 12:34 AM, Wei Liu wrote:
Cc Chen
On Mon, Mar 27, 2017 at 05:06:13AM -0400, Joshua Otto wrote:
The COLO xc domain save and restore procedures both make use of a 'postcopy'
callback to defer part of each checkpoint operation to xl. In this context, the
name 'postcopy' is meant as
All,
I am pleased to announce the release of Xen 4.8.1. This is
available immediately from its git repository
http://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=refs/heads/stable-4.8
(tag RELEASE-4.8.1) or from the XenProject download page
http://www.xenproject.org/downloads/xen-archives/xen-4
On 04/11/2017 08:15 AM, Juergen Gross wrote:
On 10/04/17 08:25, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Hi, all!
This patch series adds/updates para-virtual device
protocols for Linux Kernel (headers):
o kbdif (updated/multitouch support added)
o sndif - sound (new)
On 11/04/17 07:25, Glenn Enright wrote:
> Hi all
>
> We are seeing an odd issue with domu domains from xl destroy, under
> recent 4.9 kernels a (null) domain is left behind.
I guess this is the dom0 kernel version?
> This has occurred on a variety of hardware, with no obvious commonality.
>
> 4
flight 107353 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107353/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 4 host-ping-check-native fail REGR. vs. 107325
Regressions which are r
Hi all
We are seeing an odd issue with domu domains from xl destroy, under
recent 4.9 kernels a (null) domain is left behind.
This has occurred on a variety of hardware, with no obvious commonality.
4.4.55 does not show this behavior.
On my test machine I have the following packages installe
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Monday, April 10, 2017 9:30 PM
>
> >>> On 10.04.17 at 14:14, wrote:
> > Since c/s 92cf67888a, x86_emulate_wrapper() asserts stricter behaviour
> about
> > the relationship between X86EMUL_EXCEPTION and ctxt.event_pending.
> >
> > These remova
On 10/04/17 08:25, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Hi, all!
>
> This patch series adds/updates para-virtual device
> protocols for Linux Kernel (headers):
> o kbdif (updated/multitouch support added)
> o sndif - sound (new)
> o displif - display (new)
>
> C
On 30/03/17 22:06, Nicolai Stange wrote:
> In preparation for making the clockevents core NTP correction aware,
> all clockevent device drivers must set ->min_delta_ticks and
> ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a
> clockevent device's rate is going to change dynamical
flight 107332 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107332/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 107284
test-amd64-i386-xl-q
On Tue, Apr 11, 2017 at 3:50 AM, Stefano Stabellini
wrote:
> On Mon, 10 Apr 2017, Stefano Stabellini wrote:
>> On Mon, 10 Apr 2017, hrg wrote:
>> > On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote:
>> > > On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
>> > >> Hi,
>> > >>
>> > >> In xen_map_cache_unlocked
flight 107352 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107352/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 7a69524b288907b6d29581ddc1152b1324e13f73
baseline version:
xtf ad3af7b1acce6cf396cdb3
Hi,
I apologize to anyone who receives this twice - I received an
error/bounce message.
I am writing because I am interested in applying to Outreachy and
contributing to the Xen Code Review Dashboard. My most formal experience
with open source was in 2014 when I participated in the Ascend Project.
flight 107333 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107333/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-checkfail like 107233
test-armhf-armhf-libvirt
Hi Jan,
Thank you very much for your review comments.
I need a few clarifications to move forward.
On 4/3/2017 6:55 AM, Jan Beulich wrote:
On 31.03.17 at 17:42, wrote:
The title needs improvement - it doesn't really reflect what the
patch does.
I apologize for this. I kept the name same si
On Mon, 10 Apr 2017, Andre Przywara wrote:
> Hi,
>
> On 10/04/17 00:12, André Przywara wrote:
> > Hi,
> >
> > I wanted to run some ideas on how to prevent the race conditions we are
> > facing with the ITS emulation and removing devices and/or LPIs.
> > I think Stefano's idea of tagging a discard
flight 107331 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107331/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 1072
flight 107330 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107330/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 107247
build-armhf-xsm
On Fri, Apr 07, 2017 at 11:16:22AM +0200, Petr Tesarik wrote:
> On Wed, 5 Apr 2017 13:13:00 +0200
> Petr Tesarik wrote:
>
> > On Tue, 4 Apr 2017 12:42:53 -0700 (PDT)
> > Daniel Kiper wrote:
> >
> >[...]
> > > So, if Petr did relevant tests that is nice. However, then, IMO, this
> > > patch begs P
This run is configured for baseline tests only.
flight 71169 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71169/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1ea946d0f9ea7de963545fbe93cc7f781c03d0b2
baseline v
On Mon, 10 Apr 2017, Stefano Stabellini wrote:
> On Mon, 10 Apr 2017, hrg wrote:
> > On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote:
> > > On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
> > >> Hi,
> > >>
> > >> In xen_map_cache_unlocked(), map to guest memory maybe in entry->next
> > >> instead of first
When we concurrently try to unload and load crash
images we eventually get:
Xen call trace:
[] machine_kexec_add_page+0x3a0/0x3fa
[] machine_kexec_load+0xdb/0x107
[] kexec.c#kexec_load_slot+0x11/0x42
[] kexec.c#kexec_load+0x119/0x150
[] kexec.c#do_kexec_op_internal+0xab/0xcf
On Mon, Apr 10, 2017 at 01:23:46PM +0200, Jiri Slaby wrote:
> On 03/22/2017, 04:44 PM, Jiri Slaby wrote:
> > On 03/22/2017, 03:26 PM, Josh Poimboeuf wrote:
> >> On Mon, Mar 20, 2017 at 01:32:15PM +0100, Jiri Slaby wrote:
> >>> Somewhere END was used to end a function, elsewhere, nothing was used.
>
flight 107328 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107328/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 107238
This run is configured for baseline tests only.
flight 71168 xen-4.8-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71168/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop
On Mon, 10 Apr 2017, hrg wrote:
> On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote:
> > On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
> >> Hi,
> >>
> >> In xen_map_cache_unlocked(), map to guest memory maybe in entry->next
> >> instead of first level entry (if map to rom other than guest memory
> >> come
>> The following is meant as a real question without any prejudice:
>>
>> How old a Xen version do we want to support in the Linux kernel?
>>
>> - Only those being still maintained (meaning getting security fixes)
Definitely not this. 4.4 is the oldest version receiving official XSA
patches and i
flight 107355 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107355/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64-pvops 5 ker
On Mon, 10 Apr 2017, Juergen Gross wrote:
> On 10/04/17 17:32, Raslan, KarimAllah wrote:
> >
> > Ahmed, Karim Allah
> > karah...@amazon.de
> >
> >
> >
> >> On Apr 10, 2017, at 3:57 PM, Juergen Gross wrote:
> >>
> >> On 10/04/17 15:47, Boris Ostrovsky wrote:
> >>> On 04/07/2017 06:11 PM, Stefan
On Mon, 10 Apr 2017, Juergen Gross wrote:
> On 05/04/17 21:03, Stefano Stabellini wrote:
> > Hi all,
> >
> > This patch series implements a new transport for 9pfs, aimed at Xen
> > systems.
> >
> > The transport is based on a traditional Xen frontend and backend drivers
> > pair. This patch serie
flight 107324 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107324/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 10
flight 107327 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107327/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 10
flight 107340 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107340/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64-pvops 5 ker
Hi,
On 10/04/17 00:12, André Przywara wrote:
> Hi,
>
> I wanted to run some ideas on how to prevent the race conditions we are
> facing with the ITS emulation and removing devices and/or LPIs.
> I think Stefano's idea of tagging a discarded LPI is the key, but still
> some details are left to be
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 4ced6c0..a498ddd 100644
--- a/Osstest/TestSupport.pm
+++ b/Osstest/TestSupport.pm
@@ -814,7 +814,7 @@ sub serial_fetch
These were, anomalously, printed to stdout. We are going to want to
reserve stdout for programmatically-useful output.
Signed-off-by: Ian Jackson
---
mg-allocate |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mg-allocate b/mg-allocate
index 7b1eb62..f895af2 100755
--
This allows host allocation to be skipped even though the rest of the
job is being run.
Signed-off-by: Ian Jackson
---
ts-hosts-allocate-Executive |5 +
1 file changed, 5 insertions(+)
diff --git a/ts-hosts-allocate-Executive b/ts-hosts-allocate-Executive
index 0b83365..9417226 100755
-
Empirically, if glob cannot do its work, it sets $! and returns an
empty list.
Signed-off-by: Ian Jackson
---
Osstest/Serial/sympathy.pm |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Osstest/Serial/sympathy.pm b/Osstest/Serial/sympathy.pm
index 84a1e09..7461e07 10064
This prints RESTYPE/RESNAME/SHAREIX to stdout, after allocation is
successful (outside the db retry loop). This means that a
programmatic caller can now tell what was allocated, even if the spec
was complex.
Signed-off-by: Ian Jackson
---
mg-allocate |8
1 file changed, 8 insertion
Given a previously failed job, this will:
* Create a flight for the repro attempt
* (Optionally) allocate a host to the user's personal task
* (Optionally) wipe the host
* Install the version of Xen and Linux used by that flight
* Run the job until the specified step finishes
* Email the user
For reasons that aren't clear, perl's glob operator ignores the \n.
We can gloss over that for now, but let's chomp it in case they fix
that.
Signed-off-by: Ian Jackson
---
Osstest/Serial/sympathy.pm |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Osstest/Serial/sympat
This allows runvars to override hostflags from the resource database
or configuration.
Signed-off-by: Ian Jackson
---
Osstest/TestSupport.pm |8
1 file changed, 8 insertions(+)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index a498ddd..88b0a65 100644
--- a/Osstest/
On Mon, Apr 10, 2017 at 09:19:52AM -0600, Jan Beulich wrote:
> >>> On 10.04.17 at 15:34, wrote:
> > --- a/xen/include/asm-x86/atomic.h
> > +++ b/xen/include/asm-x86/atomic.h
> > @@ -41,20 +41,42 @@ build_add_sized(add_u64_sized, "q", uint64_t, "ri")
> > #undef build_write_atomic
> > #undef build
On 10/04/17 17:32, Raslan, KarimAllah wrote:
>
> Ahmed, Karim Allah
> karah...@amazon.de
>
>
>
>> On Apr 10, 2017, at 3:57 PM, Juergen Gross wrote:
>>
>> On 10/04/17 15:47, Boris Ostrovsky wrote:
>>> On 04/07/2017 06:11 PM, Stefano Stabellini wrote:
On Fri, 7 Apr 2017, Boris Ostrovsky wro
flight 107325 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107325/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-checkfail like 107298
test-armhf-armhf-libvirt-xsm 13
flight 107326 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107326/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xend-qemut-winxpsp3 9 windows-install fail REGR. vs. 106822
Tests which are
On Mon, Apr 10, 2017 at 04:16:12PM +0100, Andrew Cooper wrote:
> On 10/04/17 16:12, Wei Liu wrote:
> > On Mon, Apr 10, 2017 at 04:04:22PM +0100, Andrew Cooper wrote:
> >> On 10/04/17 14:27, Wei Liu wrote:
> >>> No functional change.
> >>>
> >>> Signed-off-by: Wei Liu
> >> Throughout this series, p
On Mon, Apr 10, 2017 at 04:04:22PM +0100, Andrew Cooper wrote:
> On 10/04/17 14:27, Wei Liu wrote:
> > No functional change.
> >
> > Signed-off-by: Wei Liu
>
> Throughout this series, please make sure you add in proper NULL'ing of
> freed data.
>
> While this patch is no functional change at the
Monday, April 10, 2017, 4:44:47 PM, you wrote:
> On Mon, Apr 10, 2017 at 03:21:41PM +0100, Andrew Cooper wrote:
>> On 10/04/17 15:12, Konrad Rzeszutek Wilk wrote:
>> > On Mon, Apr 10, 2017 at 02:28:58PM +0100, Wei Liu wrote:
>> >> On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
>>
Ahmed, Karim Allah
karah...@amazon.de
> On Apr 10, 2017, at 3:57 PM, Juergen Gross wrote:
>
> On 10/04/17 15:47, Boris Ostrovsky wrote:
>> On 04/07/2017 06:11 PM, Stefano Stabellini wrote:
>>> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
On 04/07/2017 01:36 PM, Stefano Stabellini wrote:
>>
Hi Roger,
On 10/04/17 14:34, Roger Pau Monne wrote:
The changes introduced on c47d1d broke the clang build due to undefined
references to __xsm_action_mismatch_detected, because clang hasn't optimized
the code properly. The following patch allows the clang build to work again,
while keeping the
On 10/04/17 16:22, Wei Liu wrote:
> On Mon, Apr 10, 2017 at 04:16:12PM +0100, Andrew Cooper wrote:
>> On 10/04/17 16:12, Wei Liu wrote:
>>> On Mon, Apr 10, 2017 at 04:04:22PM +0100, Andrew Cooper wrote:
On 10/04/17 14:27, Wei Liu wrote:
> No functional change.
>
> Signed-off-by: We
flight 107320 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107320/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 59254
test-armhf-armhf-xl
>>> On 10.04.17 at 15:34, wrote:
> clang doesn't understand the "=A" register constrain when used with 64bits
> assembly and spits out an internal error:
>
> fatal error: error in backend: Cannot select: 0x7f9fb89c9390: i64 =
> build_pair 0x7f9fb89c92b0,
> 0x7f9fb89c9320
> 0x7f9fb89c92b0
>>> On 10.04.17 at 15:34, wrote:
> --- a/xen/include/asm-x86/atomic.h
> +++ b/xen/include/asm-x86/atomic.h
> @@ -41,20 +41,42 @@ build_add_sized(add_u64_sized, "q", uint64_t, "ri")
> #undef build_write_atomic
> #undef build_add_sized
>
> -void __bad_atomic_size(void);
> +/*
> + * NB: read_atom
On 10/04/17 14:27, Wei Liu wrote:
> We want to have a single entry point to initialise hvm guest. The
> timing to set hap bit and create per domain mapping is deferred, but
> that's not a problem.
>
> No functional change.
>
> Signed-off-by: Wei Liu
Two observations...
> ---
> xen/arch/x86/dom
On 10/04/17 16:12, Wei Liu wrote:
> On Mon, Apr 10, 2017 at 04:04:22PM +0100, Andrew Cooper wrote:
>> On 10/04/17 14:27, Wei Liu wrote:
>>> No functional change.
>>>
>>> Signed-off-by: Wei Liu
>> Throughout this series, please make sure you add in proper NULL'ing of
>> freed data.
>>
>> While this
On 10/04/17 14:27, Wei Liu wrote:
> No functional change.
>
> Signed-off-by: Wei Liu
Throughout this series, please make sure you add in proper NULL'ing of
freed data.
While this patch is no functional change at the moment, you have
introduced a latent double-free bug for if (/when) pv_domain_de
Hi,
This issue came up in the #xen IRC channel on freenode, and Andrew
Cooper asked for somebody to email xen-devel so it could be fixed. A
user had the following line in their domain config and couldn't figure
out why it wasn't working correctly:
vfb=['vnclisten="10.1.1.8:2"']
The answer is, o
On Mon, Apr 10, 2017 at 03:21:41PM +0100, Andrew Cooper wrote:
> On 10/04/17 15:12, Konrad Rzeszutek Wilk wrote:
> > On Mon, Apr 10, 2017 at 02:28:58PM +0100, Wei Liu wrote:
> >> On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
> >>> On 10/04/17 12:24, lidonglin wrote:
> Hi all:
On 04/10/2017 04:41 AM, Roger Pau Monne wrote:
On Fri, Apr 07, 2017 at 08:54:59AM -0600, Jan Beulich wrote:
On 07.04.17 at 16:34, wrote:
The changes introduced on c47d1d broke the clang build due to undefined
references to __xsm_action_mismatch_detected, because clang hasn't optimized
the code
On 04/10/2017 09:34 AM, Roger Pau Monne wrote:
The changes introduced on c47d1d broke the clang build due to undefined
references to __xsm_action_mismatch_detected, because clang hasn't optimized
the code properly. The following patch allows the clang build to work again,
while keeping the same f
On 03/21/2017 07:19 PM, Juergen Gross wrote:
Setting the pointing device resolution via Xenstore isn't working
reliably: in case XenbusStateInitWait has been missed the resolution
settings won't be read. Correct this.
Cc: sta...@vger.kernel.org
Signed-off-by: Juergen Gross
---
drivers/input/m
On 10/04/17 15:12, Konrad Rzeszutek Wilk wrote:
> On Mon, Apr 10, 2017 at 02:28:58PM +0100, Wei Liu wrote:
>> On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
>>> On 10/04/17 12:24, lidonglin wrote:
Hi all:
I have one question about PCI passthrough. I fo
On 04/10/2017 05:11 PM, Juergen Gross wrote:
On 10/04/17 16:00, Oleksandr Andrushchenko wrote:
On 04/10/2017 04:50 PM, Juergen Gross wrote:
On 10/04/17 15:44, Oleksandr Andrushchenko wrote:
Hi, Juergen!
On 03/21/2017 07:19 PM, Juergen Gross wrote:
Add a parameter for setting the resolution
clang doesn't understand the "=A" register constrain when used with 64bits
assembly and spits out an internal error:
fatal error: error in backend: Cannot select: 0x7f9fb89c9390: i64 = build_pair
0x7f9fb89c92b0,
0x7f9fb89c9320
0x7f9fb89c92b0: i32,ch,glue = CopyFromReg 0x7f9fb89c9240, Regi
The changes introduced on c47d1d broke the clang build due to undefined
references to __xsm_action_mismatch_detected, because clang hasn't optimized
the code properly. The following patch allows the clang build to work again,
while keeping the same functionality.
Signed-off-by: Roger Pau Monné
--
The current code in dm_op breaks clang build with:
dm.c:411:21: error: 'break' is bound to loop, GCC binds it to switch
[-Werror,-Wgcc-compat]
while ( read_atomic(&p2m->ioreq.entry_count) &&
^
xen/include/asm/atomic.h:53:43: note: expanded from macro 'read_atomic'
On Mon, Apr 10, 2017 at 02:28:58PM +0100, Wei Liu wrote:
> On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
> > On 10/04/17 12:24, lidonglin wrote:
> > >
> > > Hi all:
> > >
> > > I have one question about PCI passthrough. I found
> > > that if I created a VM with host
On 04/10/2017 09:57 AM, Juergen Gross wrote:
> On 10/04/17 15:47, Boris Ostrovsky wrote:
>> On 04/07/2017 06:11 PM, Stefano Stabellini wrote:
>>> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
On 04/07/2017 01:36 PM, Stefano Stabellini wrote:
> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
>>
On 10/04/17 16:00, Oleksandr Andrushchenko wrote:
>
>
> On 04/10/2017 04:50 PM, Juergen Gross wrote:
>> On 10/04/17 15:44, Oleksandr Andrushchenko wrote:
>>> Hi, Juergen!
>>>
>>> On 03/21/2017 07:19 PM, Juergen Gross wrote:
Add a parameter for setting the resolution of xen-kbdfront in order
On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
> On 10/04/17 12:24, lidonglin wrote:
> >
> > Hi all:
> >
> > I have one question about PCI passthrough. I found
> > that if I created a VM with host pci device(cfg file as below), there
> > were some xenstore keys exsit
Use the correct vcpuop name and delete on trailing white space.
Signed-off-by: Wei Liu
---
xen/include/public/arch-x86/xen.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/include/public/arch-x86/xen.h
b/xen/include/public/arch-x86/xen.h
index 8a9ba7982b..f21332e897
This series refactors x86/domain.c to move HVM and PV specific code to their
respective directory.
The arch_set_info_guest is not touched yet. Refactoring that function will be
in another series because 1) I need to touch ARM code as well; 2) I need to do
some archaeology to know why it is done li
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/domain.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
index 96c777c771..ddebff6187 100644
--- a/xen/arch/x86/domain.c
+++ b/xen/arch/x86/domain.c
We want to have a single entry point to initialise hvm guest. The
timing to set hap bit and create per domain mapping is deferred, but
that's not a problem.
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/domain.c | 11 ++-
xen/arch/x86/hvm/hvm.c| 25 +
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/domain.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
index af060d8239..05885a103d 100644
--- a/xen/arch/x86/domain.c
+++ b/xen/arch/x86/domain.c
@
Lump everything PV related in arch_domain_create into
pv_domain_initialise.
Though domcr_flags is not necessary, the new function is given one to
match hvm counterpart.
Since it cleans up after itself there is no need to clean up in
arch_domain_create in case of failure.
No functional change.
S
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/domain.c | 65 ---
1 file changed, 36 insertions(+), 29 deletions(-)
diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
index 90e2b1f82a..96c777c771 100644
--- a/xen/arch/x86/do
There is only one function arch_set_info_hvm_guest is moved. The
check_segment function is also moved since arch_set_info_hvm_guest is
the only user.
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/domain.c | 291 -
xen/arch/x86/hvm/Make
Move all the PV specific code along with the supporting code to
pv/domain.c.
This in turn requires exporting a few functions in header files. Export
paravirt context switch functions in domain.h and create pv/pv.h for
the rest.
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/doma
On 04/10/2017 04:50 PM, Juergen Gross wrote:
On 10/04/17 15:44, Oleksandr Andrushchenko wrote:
Hi, Juergen!
On 03/21/2017 07:19 PM, Juergen Gross wrote:
Add a parameter for setting the resolution of xen-kbdfront in order to
be able to cope with a (virtual) frame buffer of arbitrary resolutio
On 10/04/17 15:47, Boris Ostrovsky wrote:
> On 04/07/2017 06:11 PM, Stefano Stabellini wrote:
>> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
>>> On 04/07/2017 01:36 PM, Stefano Stabellini wrote:
On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
> On 04/07/2017 07:58 AM, Ian Jackson wrote:
>> t
flight 107329 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107329/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1ea946d0f9ea7de963545fbe93cc7f781c03d0b2
baseline version:
ovmf c137d95081690d4877fbe
On 10/04/17 15:44, Oleksandr Andrushchenko wrote:
> Hi, Juergen!
>
> On 03/21/2017 07:19 PM, Juergen Gross wrote:
>> Add a parameter for setting the resolution of xen-kbdfront in order to
>> be able to cope with a (virtual) frame buffer of arbitrary resolution.
>>
>> Signed-off-by: Juergen Gross
On 04/07/2017 06:11 PM, Stefano Stabellini wrote:
> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
>> On 04/07/2017 01:36 PM, Stefano Stabellini wrote:
>>> On Fri, 7 Apr 2017, Boris Ostrovsky wrote:
On 04/07/2017 07:58 AM, Ian Jackson wrote:
> tl;dr:
> Please apply
>
> da72ff5
Hi, Juergen!
On 03/21/2017 07:19 PM, Juergen Gross wrote:
Add a parameter for setting the resolution of xen-kbdfront in order to
be able to cope with a (virtual) frame buffer of arbitrary resolution.
Signed-off-by: Juergen Gross
---
drivers/input/misc/xen-kbdfront.c | 10 --
1 file
On Mon, Apr 10, 2017 at 01:46:20PM +0100, Andrew Cooper wrote:
> On 10/04/17 12:24, lidonglin wrote:
> >
> > Hi all:
> >
> > I have one question about PCI passthrough. I found
> > that if I created a VM with host pci device(cfg file as below), there
> > were some xenstore keys exsit
Hi Wei,
On 10/04/17 10:47, Wei Liu wrote:
Cc Julien
These are small bug fixes that can be safely committed, IMHO.
Release-acked-by: Julien Grall
Cheers,
On Fri, Apr 07, 2017 at 02:27:17PM +0100, Jonathan Davies wrote:
In order to make oxenstored restartable, we need to save internal sta
On Mon, Apr 10, 2017 at 12:21:01PM +0100, George Dunlap wrote:
> On 10/04/17 11:37, George Dunlap wrote:
> > On 06/04/17 20:52, Konrad Rzeszutek Wilk wrote:
> >> On Thu, Apr 06, 2017 at 03:57:06PM +0100, George Dunlap wrote:
> >>> Signed-off-by: George Dunlap
> >>> ---
> >>> Andrew Cooper
> >>> I
>>> On 10.04.17 at 14:14, wrote:
> Since c/s 92cf67888a, x86_emulate_wrapper() asserts stricter behaviour about
> the relationship between X86EMUL_EXCEPTION and ctxt.event_pending.
>
> These removals should have been included in the aforementioned changeset, and
> were only omitted due an oversig
Since c/s 92cf67888a, x86_emulate_wrapper() asserts stricter behaviour about
the relationship between X86EMUL_EXCEPTION and ctxt.event_pending.
These removals should have been included in the aforementioned changeset, and
were only omitted due an oversight.
Signed-off-by: Andrew Cooper
---
CC: J
On 10/04/17 12:24, lidonglin wrote:
>
> Hi all:
>
> I have one question about PCI passthrough. I found
> that if I created a VM with host pci device(cfg file as below), there
> were some xenstore keys exsiting in /local/domain/0 and
> /local/domain/DomID/. Besides I found one unknow
On 17-04-10 11:27:04, Yi Sun wrote:
> On 17-04-07 03:46:42, Jan Beulich wrote:
> > >>> On 07.04.17 at 11:08, wrote:
> > > On 17-04-07 02:48:40, Jan Beulich wrote:
> > >> >>> On 07.04.17 at 07:17, wrote:
> > >> > On 17-04-06 08:02:15, Jan Beulich wrote:
> > >> >> Okay, so not the context switch pa
Unfortunately, this commit is potentially a candidate for reverting. After a
lengthy qualification I realized that there is a function called:
"xen_strict_xenbus_quirk()" that is being called in the offending path that
short-circuits the offending code!
So at the moment any domU kernel with this c
On 10/04/17 13:24, Paul Durrant wrote:
>> -Original Message-
>> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
>> Sent: 10 April 2017 13:15
>> To: Xen-devel
>> Cc: Andrew Cooper ; Jan Beulich
>> ; Tim (Xen.org) ; Paul Durrant
>> ; Jun Nakajima ; Kevin
>> Tian ; Julien Grall
>> Sub
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: 10 April 2017 13:15
> To: Xen-devel
> Cc: Andrew Cooper ; Jan Beulich
> ; Tim (Xen.org) ; Paul Durrant
> ; Jun Nakajima ; Kevin
> Tian ; Julien Grall
> Subject: [PATCH for-4.9] x86/emul: Drop more redund
On 10/04/17 11:37, George Dunlap wrote:
> On 06/04/17 20:52, Konrad Rzeszutek Wilk wrote:
>> On Thu, Apr 06, 2017 at 03:57:06PM +0100, George Dunlap wrote:
>>> Signed-off-by: George Dunlap
>>> ---
>>> Andrew Cooper
>>> Ian Jackson
>>> Jan Beulich
>>> Konrad Rzeszutek Wilk
>>> Stefano Stabellin
Hi all:
I have one question about PCI passthrough. I found that if I
created a VM with host pci device(cfg file as below), there were some xenstore
keys exsiting in /local/domain/0 and /local/domain/DomID/. Besides I found one
unknown device in device manager of Windows OS with C
1 - 100 of 145 matches
Mail list logo
