virsh cpu-models x86_64 | sort
486
Conroe
Haswell
Nehalem
Opteron_G1
Opteron_G2
Opteron_G3
Opteron_G4
Opteron_G5
Penryn
SandyBridge
Westmere
athlon
core2duo
coreduo
cpu64-rhel5
cpu64-rhel6
kvm32
kvm64
n270
pentium
pentium2
pentium3
pentiumpro
phenom
qemu32
qemu64
interesting that it doesn't have
Hi,
In KVMGT, we need to register an iodev only *after* BAR
registers are
written by guest.
Oh, the guest can write the bar register at any time. Typically it
happens at boot only, but it can also happen at runtime, for example on
reboot.
I've also seen the
On Sat, Nov 29, 2014 at 1:28 PM, Christoffer Dall
christoffer.d...@linaro.org wrote:
On Mon, Nov 24, 2014 at 11:26:51PM +0200, Nikolay Nikolaev wrote:
On IO memory abort, try to handle the MMIO access thorugh the KVM
registered read/write callbacks. This is done by invoking the relevant
On Sat, Nov 29, 2014 at 3:54 PM, Nikolay Nikolaev
n.nikol...@virtualopensystems.com wrote:
On Sat, Nov 29, 2014 at 1:29 PM, Christoffer Dall
christoffer.d...@linaro.org wrote:
On Mon, Nov 24, 2014 at 11:26:58PM +0200, Nikolay Nikolaev wrote:
In io_mem_abort remove the call to vgic_handle_mmio.
On Sat, Nov 29, 2014 at 1:29 PM, Christoffer Dall
christoffer.d...@linaro.org wrote:
Inidicate KVM in the subject please.
On Mon, Nov 24, 2014 at 11:27:06PM +0200, Nikolay Nikolaev wrote:
This enables compilation of the eventfd feature on ARM.
does this enable anything else than the
On 05/12/2014 09:50, Gerd Hoffmann wrote:
A few comments on the kernel stuff (brief look so far, also
compile-tested only, intel gfx on my test machine is too old).
* Noticed the kernel bits don't even compile when configured as
module. Everything (vgt, i915, kvm) must be compiled
(I somehow managed to review one patch twice instead of this one ...)
2014-12-04 16:57+0100, Paolo Bonzini:
From: Wanpeng Li wanpeng...@linux.intel.com
Expose the XSAVES feature to the guest if the kvm_x86_ops say it is
available.
Signed-off-by: Wanpeng Li wanpeng...@linux.intel.com
On Fri, Dec 05, 2014 at 09:50:21AM +0100, Gerd Hoffmann wrote:
https://www.usenix.org/conference/atc14/technical-sessions/presentation/tian
/me goes read this.
A few comments on the kernel stuff (brief look so far, also
compile-tested only, intel gfx on my test machine is too old).
Is virtio_mmio used only for arm emulation?
I was looking through qemu sources and the only file
that I have found to instantiate virtio-mmio proxies is arm/virt.c .
Cata
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/05/2014 03:17 AM, Thomas Lau wrote:
virsh cpu-models x86_64 | sort
...
Penryn SandyBridge Westmere
...
interesting that it doesn't have Ivy Bridge, any reason?
The reason would be that you are running an older version.
- --
All rights
On Fri, Dec 05, 2014 at 08:29:54AM +0100, Paolo Bonzini wrote:
On 05/12/2014 03:24, Konrad Rzeszutek Wilk wrote:
We could do a simple thing - which is that the paravirt_enabled
could have the value 1 for Xen and 2 for KVM. The assembler logic
would be inverted and just check for 1. I am
On Thu, Dec 04, 2014 at 02:53:26PM +0100, Paolo Bonzini wrote:
On 25/11/2014 21:24, Thomas Gleixner wrote:
On Tue, 25 Nov 2014, Rik van Riel wrote:
On 11/25/2014 12:21 PM, Marcelo Tosatti wrote:
Since lapic timer handler only wakes up a simple waitqueue,
it can be executed from
On Wed, Dec 03, 2014 at 08:39:47PM +0100, Luis R. Rodriguez wrote:
On Wed, Dec 03, 2014 at 05:37:51AM +0100, Juergen Gross wrote:
On 12/03/2014 03:28 AM, Luis R. Rodriguez wrote:
On Tue, Dec 02, 2014 at 11:11:18AM +, David Vrabel wrote:
On 01/12/14 22:36, Luis R. Rodriguez wrote:
- Original Message -
From: Rik van Riel r...@redhat.com
To: Thomas Lau t...@tetrioncapital.com, Paolo Bonzini
pbonz...@redhat.com
Cc: Yong Wang yong.y.w...@linux.intel.com, kvm kvm@vger.kernel.org
Sent: Friday, December 5, 2014 4:23:54 PM
Subject: Re: kvm ivy bridge support?
On Wed, Dec 03, 2014 at 10:18:36PM +0100, Christoffer Dall wrote:
Several people have reported problems with rebooting ARM VMs, especially
on 32-bit ARM. This is mainly due to the same reason we were seeing
boot errors in the past, namely that the ram, dcache, and icache weren't
coherent on
On Dec 5, 2014 8:09 AM, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote:
On Fri, Dec 05, 2014 at 08:29:54AM +0100, Paolo Bonzini wrote:
On 05/12/2014 03:24, Konrad Rzeszutek Wilk wrote:
We could do a simple thing - which is that the paravirt_enabled
could have the value 1 for Xen
If uio_register_device() fails in probe(), it breaks off initialization,
deallocates all resources, but returns zero.
The patch adds proper error code propagation.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov khoroshi...@ispras.ru
---
BitVisor hypervisor fails to start a nested guest due to lack of MSR
load/store support in KVM.
This patch fixes this problem according to Intel SDM.
Signed-off-by: Eugene Korenevsky ekorenev...@gmail.com
---
arch/x86/include/asm/vmx.h| 6 ++
arch/x86/include/uapi/asm/msr-index.h
paravirt_enabled has the following effects:
- Disables the F00F bug workaround warning. There is no F00F bug
workaround any more because Linux's standard IDT handling already
works around the F00F bug, but the warning still exists. This
is only cosmetic, and, in any event, there is no
On Wed, Nov 12, 2014 at 02:33:00PM +1030, Rusty Russell wrote:
Amos Kong ak...@redhat.com writes:
From: Rusty Russell ru...@rustcorp.com.au
The previous patch added one potential problem: we can still be
reading from a hwrng when it's unregistered. Add a wait for zero
in the
From: Rusty Russell ru...@rustcorp.com.au
The previous patch added one potential problem: we can still be
reading from a hwrng when it's unregistered. Add a wait for zero
in the hwrng_unregister path.
v5: reset cleanup_done flag, use compiler barrier to prevent recording.
v4: add cleanup_done
From: Rusty Russell ru...@rustcorp.com.au
Another interesting anti-pattern.
Signed-off-by: Rusty Russell ru...@rustcorp.com.au
---
drivers/char/hw_random/core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index
From: Rusty Russell ru...@rustcorp.com.au
Interesting anti-pattern.
Signed-off-by: Rusty Russell ru...@rustcorp.com.au
---
drivers/char/hw_random/core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index
From: Rusty Russell ru...@rustcorp.com.au
current_rng holds one reference, and we bump it every time we want
to do a read from it.
This means we only hold the rng_mutex to grab or drop a reference,
so accessing /sys/devices/virtual/misc/hw_random/rng_current doesn't
block on read of /dev/hwrng.
When I hotunplug a busy virtio-rng device or try to access
hwrng attributes in non-smp guest, it gets stuck.
My hotplug tests:
| test 0:
| hotunplug rng device from qemu monitor
|
| test 1:
| guest) # dd if=/dev/hwrng of=/dev/null
| hotunplug rng device from qemu monitor
|
| test 2:
|
In next patch, we use reference counting for each struct hwrng,
changing reference count also needs to take mutex_lock. Before
releasing the lock, if we try to stop a kthread that waits to
take the lock to reduce the referencing count, deadlock will
occur.
Signed-off-by: Amos Kong
From: Rusty Russell ru...@rustcorp.com.au
There's currently a big lock around everything, and it means that we
can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current)
while the rng is reading. This is a real problem when the rng is slow,
or blocked (eg. virtio_rng with qemu's
On 12/05/2014 04:50 PM, Gerd Hoffmann wrote:
A few comments on the kernel stuff (brief look so far, also
compile-tested only, intel gfx on my test machine is too old).
* Noticed the kernel bits don't even compile when configured as
module. Everything (vgt, i915, kvm) must be compiled
CC Andy :)
On 12/05/2014 09:03 PM, Paolo Bonzini wrote:
On 05/12/2014 09:50, Gerd Hoffmann wrote:
A few comments on the kernel stuff (brief look so far, also
compile-tested only, intel gfx on my test machine is too old).
* Noticed the kernel bits don't even compile when configured as
On 12/05/2014 09:54 PM, Daniel Vetter wrote:
Yeah done a quick read-through of just the i915 bits too, same comment. I
guess this is just the first RFC and the redesign we've discussed about
already with xengt is in progress somewhere?
Yes, it's marching on with Xen now. The KVM implementation
On Sat, Dec 06, 2014 at 12:16:36PM +0800, Amos Kong wrote:
When I hotunplug a busy virtio-rng device or try to access
hwrng attributes in non-smp guest, it gets stuck.
Please resend these via the linux-crypto mailing list so they
can be picked up by patchwork.
Thanks,
--
Email: Herbert Xu
31 matches
Mail list logo
