Il 06/10/2014 06:45, Oscar Garcia ha scritto:
I have a host with debian 7 (intel i7 - RAM 8GB), the guest OS is also
debian. I am running a program with some threads, every thread makes a
vmexit call. Also every thread runs in a isolated vcpu. The problem is
that the program does not run
On 2014-10-06 08:51, Paolo Bonzini wrote:
Il 06/10/2014 06:45, Oscar Garcia ha scritto:
I have a host with debian 7 (intel i7 - RAM 8GB), the guest OS is also
debian. I am running a program with some threads, every thread makes a
vmexit call. Also every thread runs in a isolated vcpu. The
* Linus Torvalds (torva...@linux-foundation.org) wrote:
On Fri, Oct 3, 2014 at 10:08 AM, Andrea Arcangeli aarca...@redhat.com wrote:
Overall this looks a fairly small change to the rmap code, notably
less intrusive than the nonlinear vmas created by remap_file_pages.
Considering that
On 3 October 2014 21:47, Will Deacon will.dea...@arm.com wrote:
On Wed, Oct 01, 2014 at 11:34:51AM +0100, Anup Patel wrote:
This patchset updates KVMTOOL to use some of the features
supported by Linux-3.16 KVM ARM/ARM64, such as:
1. Target CPU == Host using KVM_ARM_PREFERRED_TARGET vm ioctl
The VCPU target type KVM_ARM_TARGET_XGENE_POTENZA is available
in latest Linux-3.16-rcX or higher hence register aarch64 target
type for it.
This patch enables us to run KVMTOOL on X-Gene Potenza host.
Signed-off-by: Pranavkumar Sawargaonkar pranavku...@linaro.org
Signed-off-by: Anup Patel
This patchset updates KVMTOOL to use some of the features
supported by Linux-3.16 KVM ARM/ARM64, such as:
1. Target CPU == Host using KVM_ARM_PREFERRED_TARGET vm ioctl
2. Target CPU type Potenza for using KVMTOOL on X-Gene
3. PSCI v0.2 support for Aarch32 and Aarch64 guest
4. System event exit
Instead, of trying out each and every target type we should
use KVM_ARM_PREFERRED_TARGET vm ioctl to determine target type
for KVM ARM/ARM64.
If KVM_ARM_PREFERRED_TARGET vm ioctl fails then we fallback to
old method of trying all known target types.
If KVM_ARM_PREFERRED_TARGET vm ioctl succeeds
The KVM_EXIT_SYSTEM_EVENT exit reason was added to define
architecture independent system-wide events for a Guest.
Currently, it is used by in-kernel PSCI-0.2 emulation of
KVM ARM/ARM64 to inform user space about PSCI SYSTEM_OFF
or PSCI SYSTEM_RESET request.
For now, we simply treat all
If in-kernel KVM support PSCI-0.2 emulation then we should set
KVM_ARM_VCPU_PSCI_0_2 feature for each guest VCPU and also
provide arm,psci-0.2,arm,psci as PSCI compatible string.
This patch updates kvm_cpu__arch_init() and setup_fdt() as
per above.
Signed-off-by: Pranavkumar Sawargaonkar
Linus,
The following changes since commit ab3f285f227fec62868037e9b1b1fd18294a83b8:
KVM: s390/mm: try a cow on read only pages for key ops (2014-08-25 14:35:28
+0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch
On Tue, Sep 30, 2014 at 01:46:51PM +0100, Catalin Marinas wrote:
On Thu, Sep 25, 2014 at 08:42:54PM +0100, Christoffer Dall wrote:
When creating or moving a memslot, make sure the IPA space is within the
addressable range of the guest. Otherwise, user space can create too
large a memslot
Hi Catalin,
On Tue, Sep 30, 2014 at 01:39:47PM +0100, Catalin Marinas wrote:
Hi Christoffer,
On Thu, Sep 25, 2014 at 08:42:53PM +0100, Christoffer Dall wrote:
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index 7796051..048f37f 100644
--- a/arch/arm/kvm/arm.c
+++
Hello,
On Fri, Oct 03, 2014 at 11:23:53AM -0700, Linus Torvalds wrote:
On Fri, Oct 3, 2014 at 10:07 AM, Andrea Arcangeli aarca...@redhat.com wrote:
This teaches gup_fast and __gup_fast to re-enable irqs and
cond_resched() if possible every BATCH_PAGES.
This is disgusting.
Many (most?)
This
On 10/4/14 2:00 AM, Gleb Natapov wrote:
Hi,
On Tue, Sep 30, 2014 at 09:07:22PM -0500, Wei Huang wrote:
Hi Paolo and Gleb,
The attached file is a preliminary version of AMD vPMU support for KVM.
Currently I am working on a formal patch set; but realized that there are
some design choice
In the extremely unlikely event that driver initialization fails after
RX buffers are added, virtio net frees RX buffers while VQs are
still active, potentially causing device to use a freed buffer.
To fix, reset device first - same as we do on device removal.
Signed-off-by: Michael S. Tsirkin
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio net violated this
rule by using receive VQs within probe.
To fix, call virtio_enable_vqs_early before using VQs.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio console violated this
rule by adding inbufs, which causes the VQ to be used directly within
probe.
To fix, call virtio_enable_vqs_early before using VQs.
Signed-off-by: Michael
config_mutex served two purposes: prevent multiple concurrent config
change handlers, and synchronize access to config_enable flag.
Since commit dbf2576e37da0fcc7aacbfbb9fd5d3de7888a3c1
workqueue: make all workqueues non-reentrant
all workqueues are non-reentrant, and config_enable
is now
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio block violated this
rule by calling add_disk, which causes the VQ to be used directly within
probe.
To fix, call virtio_enable_vqs_early before using VQs.
Signed-off-by: Michael
virtio spec 0.9.X requires DRIVER_OK to be set before
VQs are used, but some drivers use VQs before probe
function returns.
Since DRIVER_OK is set after probe, this violates the spec.
Even though under virtio 1.0 transitional devices support this
behaviour, we want to make it possible for those
Defer config changed notifications that arrive during
probe/scan/freeze/restore.
This will allow drivers to set DRIVER_OK earlier, without worrying about
racing with config change interrupts.
This change will also benefit old hypervisors (before 2009)
that send interrupts without checking
This is in preparation to extending config changed event handling
in core.
Wrapping these in an API also seems to make for a cleaner code.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/linux/virtio.h | 6 +
drivers/virtio/virtio.c | 53
Now that virtio core ensures config changes don't
arrive during probing, drop config_enable flag
in virtio blk.
On removal, flush is now sufficient to guarantee that
no change work is queued.
This help simplify the driver, and will allow
setting DRIVER_OK earlier without losing config
change
Replace duplicated code in all transports with a single wrapper in
virtio.c.
The only functional change is in virtio_mmio.c: if a buggy device sends
us an interrupt before driver is set, we previously returned IRQ_NONE,
now we return IRQ_HANDLED.
As this must not happen in practice, this does
Now that virtio core ensures config changes don't arrive during probing,
drop config_enable flag in virtio net.
On removal, flush is now sufficient to guarantee that no change work is
queued.
This help simplify the driver, and will allow setting DRIVER_OK earlier
without losing config change
config_mutex served two purposes: prevent multiple concurrent config
change handlers, and synchronize access to config_enable flag.
Since commit dbf2576e37da0fcc7aacbfbb9fd5d3de7888a3c1
workqueue: make all workqueues non-reentrant
all workqueues are non-reentrant, and config_enable
is now
goto done;
done:
return;
is ugly, it was put there to make diff review easier.
replace by open-coded return.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Acked-by: Cornelia Huck cornelia.h...@de.ibm.com
---
drivers/net/virtio_net.c | 6 ++
1 file changed, 2
On restore, virtio pci does the following:
+ set features
+ init vqs etc - device can be used at this point!
+ set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits
This is in violation of the virtio spec, which
requires the following order:
- ACKNOWLEDGE
- DRIVER
- init vqs
- DRIVER_OK
This
Rusty, I have a mind to include this patchset for this merge window.
Any input on this?
This fixes the following virtio spec compliance issues:
1. on restore, drivers use device before setting ACKNOWLEDGE and DRIVER bits
2. on probe, drivers aren't prepared to handle config interrupts
arriving
On Mon, 6 Oct 2014 18:10:44 +0300
Michael S. Tsirkin m...@redhat.com wrote:
Replace duplicated code in all transports with a single wrapper in
virtio.c.
The only functional change is in virtio_mmio.c: if a buggy device sends
us an interrupt before driver is set, we previously returned
On Oct 3, 2014, at 3:50 PM, Radim Krčmář rkrc...@redhat.com wrote:
2014-10-02 17:52+0300, Nadav Amit:
2014-09-30 20:49+0300, Nadav Amit:
NoBigReal emulation should consider the effective address is between 0 and
0x instead of checking the logical address.
[...]
Please don’t apply this
On Mon, 6 Oct 2014 18:10:51 +0300
Michael S. Tsirkin m...@redhat.com wrote:
This is in preparation to extending config changed event handling
in core.
Wrapping these in an API also seems to make for a cleaner code.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, but virtio 9p device
adds self to channel list within probe, at which point VQ can be
used in violation of the spec.
To fix, call virtio_enable_vqs_early before using VQs.
On Mon, Oct 06, 2014 at 05:20:55PM +0200, Cornelia Huck wrote:
On Mon, 6 Oct 2014 18:10:51 +0300
Michael S. Tsirkin m...@redhat.com wrote:
This is in preparation to extending config changed event handling
in core.
Wrapping these in an API also seems to make for a cleaner code.
On Mon, 6 Oct 2014 18:10:55 +0300
Michael S. Tsirkin m...@redhat.com wrote:
Defer config changed notifications that arrive during
probe/scan/freeze/restore.
This will allow drivers to set DRIVER_OK earlier, without worrying about
racing with config change interrupts.
This change will
On Mon, 6 Oct 2014 18:10:58 +0300
Michael S. Tsirkin m...@redhat.com wrote:
Now that virtio core ensures config changes don't
arrive during probing, drop config_enable flag
in virtio blk.
On removal, flush is now sufficient to guarantee that
no change work is queued.
This help simplify
On Mon, 6 Oct 2014 18:11:05 +0300
Michael S. Tsirkin m...@redhat.com wrote:
Now that virtio core ensures config changes don't arrive during probing,
drop config_enable flag in virtio net.
On removal, flush is now sufficient to guarantee that no change work is
queued.
This help simplify the
On Mon, 6 Oct 2014 18:11:16 +0300
Michael S. Tsirkin m...@redhat.com wrote:
virtio spec 0.9.X requires DRIVER_OK to be set before
VQs are used, but some drivers use VQs before probe
function returns.
Since DRIVER_OK is set after probe, this violates the spec.
Even though under virtio 1.0
On Oct 3, 2014, at 3:49 PM, Radim Krčmář rkrc...@redhat.com wrote:
2014-10-03 00:30+0300, Nadav Amit:
KVM does not deliver x2APIC broadcast messages with physical mode. Intel SDM
(10.12.9 ICR Operation in x2APIC Mode) states: A destination ID value of
_H is used for broadcast of
On Mon, 6 Oct 2014 18:26:55 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Oct 06, 2014 at 05:20:55PM +0200, Cornelia Huck wrote:
On Mon, 6 Oct 2014 18:10:51 +0300
Michael S. Tsirkin m...@redhat.com wrote:
This is in preparation to extending config changed event handling
in
On Mon, 6 Oct 2014 18:11:19 +0300
Michael S. Tsirkin m...@redhat.com wrote:
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio net violated this
rule by using receive VQs within probe.
To fix, call virtio_enable_vqs_early
On Mon, 6 Oct 2014 18:11:22 +0300
Michael S. Tsirkin m...@redhat.com wrote:
virtio spec requires drivers to set DRIVER_OK before using VQs.
This is set automatically after probe returns, virtio block violated this
rule by calling add_disk, which causes the VQ to be used directly within
probe.
On Mon, Oct 06, 2014 at 02:41:18PM +0100, Christoffer Dall wrote:
On Tue, Sep 30, 2014 at 01:39:47PM +0100, Catalin Marinas wrote:
On Thu, Sep 25, 2014 at 08:42:53PM +0100, Christoffer Dall wrote:
@@ -572,19 +614,36 @@ void kvm_free_stage2_pgd(struct kvm *kvm)
return;
On Mon, Oct 06, 2014 at 02:47:01PM +0100, Christoffer Dall wrote:
On Tue, Sep 30, 2014 at 01:46:51PM +0100, Catalin Marinas wrote:
On Thu, Sep 25, 2014 at 08:42:54PM +0100, Christoffer Dall wrote:
When creating or moving a memslot, make sure the IPA space is within the
addressable range
Hello,
On Mon, Oct 06, 2014 at 09:55:41AM +0100, Dr. David Alan Gilbert wrote:
* Linus Torvalds (torva...@linux-foundation.org) wrote:
On Fri, Oct 3, 2014 at 10:08 AM, Andrea Arcangeli aarca...@redhat.com
wrote:
Overall this looks a fairly small change to the rmap code, notably
On Sat, Oct 04, 2014 at 10:23:32AM +0300, Gleb Natapov wrote:
On Tue, Sep 09, 2014 at 12:28:11PM -0300, Marcelo Tosatti wrote:
On Mon, Jul 21, 2014 at 04:14:24PM +0300, Gleb Natapov wrote:
On Wed, Jul 09, 2014 at 04:12:53PM -0300, mtosa...@redhat.com wrote:
Reload remote vcpus MMU from
Hi,
On Sat, Oct 04, 2014 at 08:13:36AM +0900, Mike Hommey wrote:
On Fri, Oct 03, 2014 at 07:07:58PM +0200, Andrea Arcangeli wrote:
MADV_USERFAULT is a new madvise flag that will set VM_USERFAULT in the
vma flags. Whenever VM_USERFAULT is set in an anonymous vma, if
userland touches a still
On Mon, Oct 06, 2014 at 01:45:24PM +0900, Oscar Garcia wrote:
Hello,
I have a question about parallel vmexit calls, I would appreciate
any answer or suggestion.
I have a host with debian 7 (intel i7 - RAM 8GB), the guest OS is
also debian. I am running a program with some threads, every
2014-10-06 18:29+0300, Nadav Amit:
On Oct 3, 2014, at 3:49 PM, Radim Krčmář rkrc...@redhat.com wrote:
2014-10-03 00:30+0300, Nadav Amit:
Reviewed-by: Radim Krčmář rkrc...@redhat.com
+#define X2APIC_BROADCAST 0xul
(int is better -- using long introduces an
2014-10-03 01:10+0300, Nadav Amit:
If DR4/5 is accessed when it is unavailable (since CR4.DE is set), then #UD
should be generated even if CPL0. This is according to Intel SDM Table 6-2:
Priority Among Simultaneous Exceptions and Interrupts.
Note, that this may happen on the first DR access,
2014-10-03 01:10+0300, Nadav Amit:
DR7.LE should be cleared during task-switch. This feature is poorly
documented.
For reference, see:
http://pdos.csail.mit.edu/6.828/2005/readings/i386/s12_02.htm
SDM [17.2.4]:
This feature is not supported in the P6 family processors, later IA-32
On Mon, Oct 06, 2014 at 04:54:46PM +0100, Catalin Marinas wrote:
On Mon, Oct 06, 2014 at 02:41:18PM +0100, Christoffer Dall wrote:
On Tue, Sep 30, 2014 at 01:39:47PM +0100, Catalin Marinas wrote:
On Thu, Sep 25, 2014 at 08:42:53PM +0100, Christoffer Dall wrote:
@@ -572,19 +614,36 @@ void
The following two patches fixup some missing memory handling in
KVM/arm64.
The first patch supports 48 bit virtual address space which involves
supporting a different number of levels of page tables in the host
kernel and the stage-2 page tables.
The second patch ensures userspace cannot create
Now when KVM has been reworked to support 48-bits host VA space, we can
allow systems to be configured with this option. However, the ARM SMMU
driver also needs to be tweaked for 48-bit support so only allow the
config option to be set when not including support for theSMMU.
Signed-off-by:
When creating or moving a memslot, make sure the IPA space is within the
addressable range of the guest. Otherwise, user space can create too
large a memslot and KVM would try to access potentially unallocated page
table entries when inserting entries in the Stage-2 page tables.
Signed-off-by:
This patch adds the necessary support for all host kernel PGSIZE and
VA_SPACE configuration options for both EL2 and the Stage-2 page tables.
However, for 40bit and 42bit PARange systems, the architecture mandates
that VTCR_EL2.SL0 is maximum 1, resulting in fewer levels of stage-2
pagge tables
2014-10-03 01:10+0300, Nadav Amit:
When read access is performed using a readable code segment, the conforming
and non-conforming checks should not be done. As a result, read using
non-conforming readable code segment fails.
This is according to Intel SDM 5.6.1 (Accessing Data in Code
2014-10-03 01:10+0300, Nadav Amit:
Once an instruction crosses a page boundary, the size read from the second
page
disregards the common case that part of the operand resides on the first page.
As a result, fetch of long insturctions may fail, and thereby cause the
decoding to fail as well.
2014-10-03 01:10+0300, Nadav Amit:
Setting the TSC deadline MSR that are initiated by the host (using ioctl's)
may
cause superfluous interrupt. This occurs in the following case:
1. A TSC deadline timer interrupt is pending.
2. TSC deadline was still not cleared (which happens during
05.10.2014 19:44, Michael S. Tsirkin пишет:
OK but pls cleanup indentation, it's all scrambled. You'll also need
to add proper attribution (using From: header), your signature etc.
Don't understand what's wrong with indentation.
--
To unsubscribe from this list: send the line unsubscribe kvm
07.10.2014 7:42, Dmitry Petuhov пишет:
05.10.2014 19:44, Michael S. Tsirkin пишет:
OK but pls cleanup indentation, it's all scrambled. You'll also need
to add proper attribution (using From: header), your signature etc.
Don't understand what's wrong with indentation.
Oh. Didn't mentioned what
61 matches
Mail list logo
