> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: Wednesday, November 28, 2018 6:06 PM
>
> Some prototypes in include/asm-x86/hvm/vmx/vmx.h have no related
> implementation. Remove them.
>
> Signed-off-by: Juergen Gross
Acked-by: Kevin Tian
___
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Tuesday, November 20, 2018 10:37 PM
>
> With PVRDTSCP mode removed, handling of MSR_TSC_AUX can move into
> the common
> code. Move its storage into struct vcpu_msrs (dropping the HVM-specific
> msr_tsc_aux), and add an RDPID featur
> From: Roger Pau Monné [mailto:roger@citrix.com]
> Sent: Wednesday, November 28, 2018 5:20 PM
>
> On Thu, Nov 01, 2018 at 09:18:14AM +, Andrew Cooper wrote:
> > On 01/11/2018 00:40, Tian, Kevin wrote:
> > >> From: Tian, Kevin
> > >> Sent: Tuesday, October 30, 2018 3:00 PM
> > >>
> > >>> F
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.20a-rc5-tag
xen: fixes for 4.20-rc5
It contains the following fixes:
- A revert of a previous commit as it is no longer necessary and has
shown to cause problems in some memory ho
flight 130867 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130867/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install
fail REGR. vs. 130155
flight 130874 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130874/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd 8a8f133349b01913412f09f2cf494bc72daf0b46
baseline version:
freebsd b1f31943cb6
flight 130913 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130913/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 82855aba5bf91e50c81526167c11d4aeaf665e66
baseline version:
xen 901a
flight 130871 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130871/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 7 xen-boot fail REGR. vs.
130373
test-amd64-i386-xl
On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be gener
On Fri, Nov 30, 2018 at 02:22:29PM +0100, Christoph Hellwig wrote:
> Return DMA_MAPPING_ERROR instead of 0 on a dma mapping failure and let
> the core dma-mapping code handle the rest.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Konrad Rzeszutek Wilk
> ---
> drivers/xen/swiotlb-xen.c | 1
flight 130869 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130869/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-xsm 7 xen-boot fail in 130840 pass in 130869
test-amd64-i386-xl-qemuu-debianhvm-
From: Dwayne Litzenberger
Signed-off-by: Dwayne Litzenberger
---
drivers/xen/xen-pciback/conf_space_header.c | 24 --
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/drivers/xen/xen-pciback/conf_space_header.c
b/drivers/xen/xen-pciback/conf_space_header.c
ind
I've got this patch series from Dwayne Litzenberger, as a fix for AMD GPU
passthrough. I don't have this hardware myself, so I can't test this, but he
claims it works. I'm not sure if allowing guest to enable/disable expansion ROM
is safe thing to do, but the comment in rom_write for me suggests it
From: Dwayne Litzenberger
Newer AMD GPUs store their initialization routines as bytecode on the
ROM. This fixes the following initialization error inside the VM when
doing PCI passthrough:
radeon :00:05.0: Invalid PCI ROM header signature: expecting 0xaa55,
got 0x
radeon :0
Hi,
On 01/12/2018 01:33, Christopher Clark wrote:
> * x86 PV domains are notified via event channel.
>
> PV guests are known to have the event channel software present in the guest
> kernel, so it is fine to depend on and use it.
>
> * x86 HVM domains and all ARM domains are notified via VIRQ.
>
On 01/12/2018 01:32, Christopher Clark wrote:
> diff --git a/xen/include/public/argo.h b/xen/include/public/argo.h
> index 20dabc0..5ad8e2b 100644
> --- a/xen/include/public/argo.h
> +++ b/xen/include/public/argo.h
> @@ -21,6 +21,20 @@
>
> #include "xen.h"
>
> +#define ARGO_RING_MAGIC
flight 130878 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130878/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install
fail REGR. vs. 129996
flight 130876 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130876/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-examine 8 reboot fail REGR. vs. 128858
test-amd64-i386-libv
Hello,
I have dual socket server with the following processor:
[root@xrtmia-09-01 ~]# head /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 1
model name : AMD EPYC 7281 16-Core Processor
stepping: 2
Which has highlighted a issu
The pull request you sent on Sun, 2 Dec 2018 10:03:25 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-4.20a-rc5-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/292974c5acae330186cbf5a833385f666aeb12c0
Thank you!
--
Deet-doot-dot,
On 11/30/2018 2:33 PM, Boris Ostrovsky wrote:
On 11/30/18 4:49 PM, Manjunath Patil wrote:
Thank you Boris for your comments. I removed faulty email of mine.
replies inline.
On 11/30/2018 12:42 PM, Boris Ostrovsky wrote:
On 11/29/18 12:17 AM, Manjunath Patil wrote:
Hi,
Feel free to suggest/co
flight 130889 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130889/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-xtf-amd64-amd64-2 69 xtf/test-hvm64-xsa-278 fail blocked in 129810
test-xtf-amd64-amd64-4 50 xt
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.
Cc: Roger Pau Monné
Cc: Jan Beulich
Signed-off-by: Zhao Yan
---
hw/x
flight 130890 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130890/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stopfail REGR. vs. 130212
test-amd64-i386
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20181203023728.26774-1-yan.y.z...@intel.com
Type: series
Subject: [Qemu-devel] [PATCH] xen/pt: Fix a xen passthrough failure
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$
Hi Mike,
On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote:
>
> On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> > Previouly drivers have their own way of mapping range of
> > kernel pages/memory into user vma and this was done by
> > invoking vm_insert_page() within a loop.
>
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.
v2: fix some coding style issue
Cc: Roger Pau Monné
Cc: Jan Beulich
S
On Mon, Dec 03, 2018 at 09:51:45AM +0530, Souptick Joarder wrote:
> Hi Mike,
>
> On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote:
> >
> > On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> > > Previouly drivers have their own way of mapping range of
> > > kernel pages/memory i
On 01/12/2018 03:10, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/xen/pvcalls-front.c: In function 'pvcalls_front_sendmsg':
> drivers/xen/pvcalls-front.c:506:25: warning:
> variable 'bedata' set but not used [-Wunused-but-set-variable]
>
> drivers/xen/pvcalls-fr
On 22/11/2018 08:18, Xin Li wrote:
> From: Talons Lee
>
> Commit e657fcc clears cpu x2apic capability bit instead of using fake
> cpuid value. However, with cpuid x2apic bit on, xen_read_msr_safe() will
> not clear the EXTD bit, which leads to uncessary msr write trying to
> disable x2apic in __x
On 03/12/2018 08:00, Juergen Gross wrote:
> On 22/11/2018 08:18, Xin Li wrote:
>> From: Talons Lee
>>
>> Commit e657fcc clears cpu x2apic capability bit instead of using fake
>> cpuid value. However, with cpuid x2apic bit on, xen_read_msr_safe() will
>> not clear the EXTD bit, which leads to unces
31 matches
Mail list logo
