Froze again :( would it be worth upgrading to a new kernel on the host instead
of using the stock once from CentOS 6.4 ? I am not overcommitting memory of the
machine so believe that is ruled out. I installed watchdog on the guest as-well
to reboot it this happened again but that did not work :(
Let mmio spte only use bit62 and bit63 on upper 32 bits, then bit 52 ~ bit 61
can be used for other purposes
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/vmx.c |4 ++--
arch/x86/kvm/x86.c |8 +++-
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/a
Store the generation-number into bit3 ~ bit11 and bit52 ~ bit61, totally
19 bits can be used, it should be enough for nearly all most common cases
In this patch, the generation-number is always 0, it will be changed in
the later patch
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c
Then it has chance to trigger mmio generation number wrap-around
Signed-off-by: Xiao Guangrong
---
arch/x86/include/asm/kvm_host.h |1 +
arch/x86/kvm/mmu.c |8
virt/kvm/kvm_main.c |6 ++
3 files changed, 15 insertions(+), 0 deletions(-)
diff --g
It is useful for debug mmio spte invalidation
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |9 +++--
arch/x86/kvm/mmutrace.h | 24
2 files changed, 31 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 1020152
Changelog in v2:
- rename kvm_mmu_invalid_mmio_spte to kvm_mmu_invalid_mmio_sptes
- use kvm->memslots->generation as kvm global generation-number
- fix comment and codestyle
- init kvm generation close to mmio wrap-around value
- keep kvm_mmu_zap_mmio_sptes
The current way is holding hot
Define some meaningful names instead of raw code
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 15 +--
arch/x86/kvm/mmu.h | 14 ++
arch/x86/kvm/vmx.c |4 ++--
3 files changed, 21 insertions(+), 12 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/k
This patch tries to introduce a very simple and scale way to invalid all
mmio sptes - it need not walk any shadow pages and hold mmu-lock
KVM maintains a global mmio invalid generation-number which is stored in
kvm->memslots.generation and every mmio spte stores the current global
generation-numbe
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I will start by reviewing the test code, so we can agree on expected
syntax/behavior, before reviewing the implementation:
On Fri, Mar 29, 2013 at 06:14:08PM +0100, Jiří Župka wrote:
> Signed-off-by: Jiří Župka
> ---
> virttest/cartesian_config_unittest.py | 79
> +++
Sorry for not reading the commit message before my previous reply. Now I
see the origin of the ">" syntax.
On Fri, Mar 29, 2013 at 06:14:07PM +0100, Jiří Župka wrote:
[...]
>
> For filtering of named variants is used character ">" because there was
> problem with conflict with = in expression key
On Fri, Mar 29, 2013 at 06:14:09PM +0100, Jiří Župka wrote:
> If default variant is not filtered by only or no filters then
> only default variant is chosen. This behavior was used for optimizing
> of speed of Cartesian config.
> If variants don't have default variant then everything works as usual
On Fri, Mar 29, 2013 at 4:12 PM, H. Peter Anvin wrote:
>
> Is there any preferred way to busy-wait on a virtio event? As in: the
> guest doesn't have anything useful to do until something is plopped down
> on the virtio queue, but would like to proceed as quickly as possible
> after that. Passin
Unedited scripts/update-linux-headers.sh run against v3.9-rc2 tag
Signed-off-by: Alex Williamson
---
linux-headers/linux/vfio.h |9 +
1 file changed, 9 insertions(+)
diff --git a/linux-headers/linux/vfio.h b/linux-headers/linux/vfio.h
index f787b72..e094121 100644
--- a/linux-header
Kernel-side vfio virtualizes all of config space, but some parts are
unique to Qemu. For instance we may or may not expose the ROM BAR,
Qemu manages MSI/MSIX, and Qemu manages the multi-function bit so that
single function devices can appear as multi-function and vica versa.
Generalize this into a
Windows seems to pay particular interest to the PCIe header type of
devices and will fail to load drivers if we attach Endpoint devices or
Legacy Endpoint devices to the Root Complex. We can use
pci_bus_is_express and pci_bus_is_root to determine the bus type and
mangle the type appropriately:
*
Graphics cards have a number of different backdoors. Some of these
are alternative ways to get PCI BAR addresses, some of them are
complete mirrors of PCI config space available through MMIO and
I/O port access. These quirks cover a number of ATI Radeon and
Nvidia devices. On the ATI/AMD side, t
Often when debugging it's useful to be able to disable bypass paths
so no interactions with the device are missed. Add some extra debug
options to do this. Also add device info on read/write BAR accesses,
which is useful when debugging more than one assigned device. A
couple DPRINTFs also had re
Guests may leave devices in a low power state at reboot, but we expect
devices to be woken up for the next boot. Make this happen.
Signed-off-by: Alex Williamson
---
hw/vfio_pci.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/hw/vfio_pci.c b/hw/vfio_pci.c
index
Hi Anthony,
The following changes since commit 174d4d215fb49b4d43196e62f22c2533431b260e:
tcg/mips: Implement muls2_i32 (2013-04-01 18:49:17 +0200)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for-qemu-20130401.0
for you to fetch changes up t
Signed-off-by: Alex Williamson
---
hw/vfio_pci.c |5 +
1 file changed, 5 insertions(+)
diff --git a/hw/vfio_pci.c b/hw/vfio_pci.c
index d310730..0d2a445 100644
--- a/hw/vfio_pci.c
+++ b/hw/vfio_pci.c
@@ -30,6 +30,7 @@
#include "qemu/event_notifier.h"
#include "exec/address-spaces.h"
#
Starting to get messy, put the back in alphabetical order.
Signed-off-by: Alex Williamson
---
hw/vfio_pci.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/hw/vfio_pci.c b/hw/vfio_pci.c
index 0d2a445..693a9ff 100644
--- a/hw/vfio_pci.c
+++ b/hw/vfio_pci.c
@@ -19,
Most VGA cards need some kind of quirk to fully operate since they
hide backdoors to get to other registers outside of PCI config space
within the registers, but this provides the base infrastructure. If
we could identity map PCI resources for assigned devices we would need
a lot fewer quirks.
To
v2 addresses some requested changes, such as the use of a file descriptor
instead of an ad-hoc handle array, and the use of an enableable
IRQ-type-specific capability to bind the vcpu to a particular MPIC device
(among other things, this allows the notifier patch to go away).
Some other requested
Remove some parts of the code that are obviously QEMU or Raven specific
before fixing style issues, to reduce the style issues that need to be
fixed.
Signed-off-by: Scott Wood
---
arch/powerpc/kvm/mpic.c | 344 ---
1 file changed, 344 deletions(-)
di
Hook the MPIC code up to the KVM interfaces, add locking, etc.
TODO: irqfd support, split up into multiple patches, KVM_IRQ_LINE
support
Signed-off-by: Scott Wood
---
Documentation/virtual/kvm/devices/mpic.txt | 37 ++
arch/powerpc/include/asm/kvm_host.h|8 +-
arch/powerpc/include
This is QEMU's hw/openpic.c from commit
abd8d4a4d6dfea7ddea72f095f993e1de941614e ("Update version for
1.4.0-rc0"), run through Lindent with no other changes to ease merging
future changes between Linux and QEMU. Remaining style issues
(including those introduced by Lindent) will be fixed in a late
Remove braces that Linux style doesn't permit, remove space after
'*' that Lindent added, keep error/debug strings contiguous, etc.
Substitute type names, debug prints, etc.
Signed-off-by: Scott Wood
---
arch/powerpc/kvm/mpic.c | 445 ++-
1 file chan
Enabling this capability connects the vcpu to the designated in-kernel
MPIC. Using explicit connections between vcpus and irqchips allows
for flexibility, but the main benefit at the moment is that it
simplifies the code -- KVM doesn't need vm-global state to remember
which MPIC object is associat
Currently, devices that are emulated inside KVM are configured in a
hardcoded manner based on an assumption that any given architecture
only has one way to do it. If there's any need to access device state,
it is done through inflexible one-purpose-only IOCTLs (e.g.
KVM_GET/SET_LAPIC). Defining n
"Michael S. Tsirkin" writes:
> Rusty's currently doing some reorgs of -net let's delay
> cleanups there to avoid stepping on each other's toys.
> Let's focus on scsi here.
> E.g. any chance framing assumptions can be fixed in 3.10?
I am waiting for your removal of the dma-compelete ordering stuff
On Sun, 2013-03-31 at 10:37 +0300, Michael S. Tsirkin wrote:
> On Fri, Mar 29, 2013 at 04:33:11AM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > This patch adds a number of virtio_queue_valid() checks to virtio-pci
> > ahead of virtio_queue_get_num() usage in order to sk
On Sun, 2013-03-31 at 10:45 +0300, Michael S. Tsirkin wrote:
> On Fri, Mar 29, 2013 at 04:33:12AM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > With the virtio_queue_valid() checks in place to skip uninitialized VQs
> > within virtio-pci code, go ahead and skip the same
On Sun, 2013-03-31 at 10:46 +0300, Michael S. Tsirkin wrote:
> On Fri, Mar 29, 2013 at 04:33:09AM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > Hi folks,
> >
> > This series adds a virtio_queue_valid() for use by virtio-pci code in
> > order to prevent opreations upon
From: Nicholas Bellinger
Hi folks,
This series adds a virtio_queue_valid() for use by virtio-pci code in
order to prevent opreations upon uninitialized VQs, which is currently
expected to occur during seabios setup of virtio-scsi with in-flight
vhost-scsi-pci device code.
On the vhost side, it
From: Michael S. Tsirkin
virtio scsi makes it legal to only setup a subset of rings. The only
way to detect the ring is setup seems to be to check whether PA was
written to. Add API to do this, and teach code to use it instead of
checking hardware queue size.
(nab: use .vring.desc instead of .
From: Nicholas Bellinger
This patch adds a number of virtio_queue_valid() checks to virtio-pci
ahead of virtio_queue_get_num() usage in order to skip operation upon
the detection of an uninitialized VQ.
There is one exception in virtio_ioport_read():VIRTIO_PCI_QUEUE_NUM,
where virtio_queue_get_n
From: Nicholas Bellinger
This patch adds virtio_queue_valid() checks in vhost_virtqueue_start()
and vhost_virtqueue_stop() to avoid uninitialized VQs during vhost-scsi-pci
seabios operation, where we currently expect only the request VQ to have
been initialized before virtio-scsi LLD guest hand-o
On Fri, 2013-03-29 at 09:14 +0100, Paolo Bonzini wrote:
> Il 29/03/2013 03:53, Nicholas A. Bellinger ha scritto:
> > On Thu, 2013-03-28 at 06:13 -0400, Paolo Bonzini wrote:
> >>> I think it's the right thing to do, but maybe not the right place
> >>> to do this, need to reset after all IO is done,
Hi,
I am looking into hw/vga.c and hw/vga-pci.c as a starting point in my
effort to get vbox svga card into kvm.
However, given my very basic understanding of VGA/SVGA standards, can
somebody throw some light on the inner workings of the std vga card in kvm?
Also, are there any good
Hi, Nicholas
Have this serial been merged to qemu 1.4? If not, I am rebasing it to
upstream, hope no one else is working on that.
> From: Nicholas Bellinger
>
> Hello Anthony & Co,
>
> This is the fourth installment to add host virtualized target support for
> the mainline tcm_vhost fabric dr
Hello Wenchao,
On Tue, 2013-04-02 at 11:28 +0800, Wenchao Xia wrote:
> Hi, Nicholas
> Have this serial been merged to qemu 1.4?
Not just yet. Asias, MST, Paolo and myself have been working recently
on the series for qemu 1.4.
> If not, I am rebasing it to
> upstream, hope no one else is work
42 matches
Mail list logo
