On Tue, Sep 13, 2011 at 02:57:20PM +0900, Isaku Yamahata wrote:
> On Sun, Sep 11, 2011 at 12:05:17PM +0300, Michael S. Tsirkin wrote:
> > On Sat, Sep 10, 2011 at 02:43:11AM +0900, Isaku Yamahata wrote:
> > > pci/pcie hot plug needs clean up for multifunction hotplug in long term.
> > > Only single
> From: Jan Kiszka
> Sent: Tuesday, September 13, 2011 12:58 AM
>
> The threaded IRQ handler for MSI-X has almost nothing in common with the
> INTx/MSI handler. Move its code into a dedicated handler.
if it's desired to further go down this cleanup path, there's also no need to
register ack notif
On Sun, Sep 11, 2011 at 12:05:17PM +0300, Michael S. Tsirkin wrote:
> On Sat, Sep 10, 2011 at 02:43:11AM +0900, Isaku Yamahata wrote:
> > pci/pcie hot plug needs clean up for multifunction hotplug in long term.
> > Only single function device case works. Multifunction case is broken
> > somwehat.
On Fri, Sep 9, 2011 at 10:44 PM, Marcelo Tosatti wrote:
> On Thu, Sep 08, 2011 at 06:11:07PM +0800, Zhi Yong Wu wrote:
>> Note:
>> 1.) When bps/iops limits are specified to a small value such as 511
>> bytes/s, this VM will hang up. We are considering how to handle this senario.
>
> You can
Hi,
On Wed, Sep 7, 2011 at 12:06 AM, Avi Kivity wrote:
> On 09/07/2011 02:20 AM, Linus Torvalds wrote:
>>
>> On Mon, Sep 5, 2011 at 2:42 AM, Avi Kivity wrote:
>> > Linus, please pull from
>> >
>> > git://github.com/avikivity/kvm.git kvm-updates/3.1
>> >
>> > to receive a fix for a build fai
Hey guys,
I was able to boot the instance with Knopix and add the append="ide=nodma" line
which got me up and running but the instance seems to lock up frequently. I'm
wondering if there are some kvm tweaks I can make to stabilize the system. Here
is what my qemu-kvm options look like:
/usr/lib
On Wed, Sep 7, 2011 at 3:07 AM, Amos Kong wrote:
> System services on guest and host take uncertain resource, it effects
> the perf results. We can use the below two scripts to disable some
> services of host and guest.
>
> stop_serivices_perf.sh is used to stop the running serivices.
> off_servic
On 2011-09-12 19:56, Chris Friesen wrote:
>
> Hi,
>
> I've been away a bit but I'm now coming back to this issue.
>
> Is it expected that the kvm-kmod modules will allow PCI device
> assignment (aka VT-d) with older kernels? If so, then is there an
> expectation for how far back it will be supp
Hi,
I've been away a bit but I'm now coming back to this issue.
Is it expected that the kvm-kmod modules will allow PCI device
assignment (aka VT-d) with older kernels? If so, then is there an
expectation for how far back it will be supported? I haven't seen a
clear statement of this anywh
Signed-off-by: Sasha Levin
---
tools/kvm/virtio/9p.c |2 +-
tools/kvm/virtio/balloon.c |2 +-
tools/kvm/virtio/blk.c |2 +-
tools/kvm/virtio/console.c |2 +-
tools/kvm/virtio/net.c |2 +-
tools/kvm/virtio/rng.c |2 +-
6 files changed, 6 insertions(+), 6 de
'kvm run' will now create a 'default' profile and boot into it.
Currently we boot into rw rootfs of the host, which is risky. Instead,
we can boot in a 'safe' enviroment with networking.
Signed-off-by: Sasha Levin
---
tools/kvm/builtin-run.c | 13 ++---
tools/kvm/builtin
On 9/11/11 9:30 PM, "Sridhar Samudrala" wrote:
> On 9/11/2011 6:18 AM, Roopa Prabhu wrote:
>>
>>
>> On 9/11/11 2:44 AM, "Michael S. Tsirkin" wrote:
>>
AFAIK, though it might maintain a single filter table space in hw, hw does
know which filter belongs to which VF. And the OS driv
On 9/11/11 12:03 PM, "Michael S. Tsirkin" wrote:
> On Sun, Sep 11, 2011 at 06:18:01AM -0700, Roopa Prabhu wrote:
>>
>>
>>
>> On 9/11/11 2:44 AM, "Michael S. Tsirkin" wrote:
>>
>>>
>>> Yes, but what I mean is, if the size of the single filter table
>>> is limited, we need to decide how ma
The threaded IRQ handler for MSI-X has almost nothing in common with the
INTx/MSI handler. Move its code into a dedicated handler.
Signed-off-by: Jan Kiszka
---
virt/kvm/assigned-dev.c | 32 +++-
1 files changed, 19 insertions(+), 13 deletions(-)
diff --git a/virt/
This API is only avaliable from python 2.6 onwards, so use
isAlive, which does exist under 2.4.
Signed-off-by: Lucas Meneghel Rodrigues
---
client/virt/virt_test_utils.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/client/virt/virt_test_utils.py b/client/virt/virt_t
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
assumes it is only called by one instance at a time for some device. So
two loops doing
echo 1 > /sys/bus/pci/devices//reset
in
pci_block_user_cfg_access was designed for the use case that a single
context, the IPR driver, temporarily delays user space accesses to the
config space via sysfs. This assumption became invalid by the time
pci_dev_reset was added as locking instance. Today, if you run two loops
in parallel that r
The new PCI API provides both generic probing for 2.3 masking support
and check&mask in the interrupt handler.
Signed-off-by: Jan Kiszka
---
drivers/uio/uio_pci_generic.c | 84 +++-
1 files changed, 7 insertions(+), 77 deletions(-)
diff --git a/drivers/uio/
These new PCI services allow to probe for 2.3-compliant INTx masking
support and then use the feature from PCI interrupt handlers. The
services are properly synchronized with concurrent config space access
via sysfs or on device reset.
This enables generic PCI device drivers like uio_pci_generic o
Richard W.M. Jones redhat.com> writes:
>
> On Sat, Jul 05, 2008 at 02:16:34PM +0300, Avi Kivity wrote:
> > Richard W.M. Jones wrote:
> >> I've been trying out RHL6.2 [sic] on KVM 70. This has an ancient
> >> 2.2.14 kernel and generally dates from 1999/2000. However it does run
> >> nicely in 1
On 9/11/11 11:52 AM, "Michael S. Tsirkin" wrote:
> On Sun, Sep 11, 2011 at 06:18:02AM -0700, Roopa Prabhu wrote:
>>
>>
>>
>> On 9/11/11 2:38 AM, "Michael S. Tsirkin" wrote:
>>
>>> On Fri, Sep 09, 2011 at 09:33:33AM -0700, Roopa Prabhu wrote:
>>>
>>> It's probably more interesting for a
On 09/12/2011 08:15 AM, Jan Kiszka wrote:
On 2011-09-12 15:12, Anthony Liguori wrote:
On 09/12/2011 08:07 AM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
- Device state visualization
Wow, still that controversial?
No, I just wanted to chat a
On 09/12/2011 08:07 AM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
- Device state visualization
Regards,
Anthony Liguori
Thanks, Juan.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@v
On 2011-09-12 15:12, Anthony Liguori wrote:
> On 09/12/2011 08:07 AM, Juan Quintela wrote:
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> - Device state visualization
Wow, still that controversial?
Reminds me that you asked me for some visitor adaption I haven'
Hi
Please send in any agenda items you are interested in covering.
Thanks, 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
On Sun, Sep 11, 2011 at 11:23:02AM +0300, Avi Kivity wrote:
> The TEST instruction doesn't write its destination operand. This
> could cause problems if an MMIO register was accessed using the TEST
> instruction. Recently Windows XP was observed to use TEST against
> the APIC ICR; this can cause
On Mon, Sep 12, 2011 at 11:26:22AM +0200, Jan Kiszka wrote:
> The use of printk_ratelimit is discouraged, replace it with
> pr*_ratelimited or __ratelimit. While at it, convert remaining
> guest-triggerable printks to rate-limited variants.
>
> Signed-off-by: Jan Kiszka
> ---
> arch/x86/kvm/i825
On Sun, Sep 11, 2011 at 10:16:20AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> We only perform work in kvm_assigned_dev_ack_irq if the guest IRQ is of
> INTx type. This completely avoids the callback invocation in non-INTx
> cases by registering the IRQ ack notifier only for INTx.
>
> Signed
On Mon, Sep 12, 2011 at 07:50:35AM -0400, Sethi Varun-B16395 wrote:
> > - kvm->arch.iommu_domain = iommu_domain_alloc();
> > + kvm->arch.iommu_domain = iommu_domain_alloc(&pci_bus_type);
>
> Although it might require changes starting all the way from the qemu
> interface, but
> it would certa
On Mon, Sep 12, 2011 at 08:08:41AM -0400, Sethi Varun-B16395 wrote:
> > The IOMMUs are usually devices on the bus itself, so they are initialized
> > after the bus is set up and the devices on it are populated. So the
> > function can not be called on bus initialization because the IOMMU is not
>
On Mon, Sep 12, 2011 at 07:56:07AM -0300, Marcelo Tosatti wrote:
> On Mon, Sep 12, 2011 at 07:21:48AM -0300, Marcelo Tosatti wrote:
> > > We could, for example, keep a stub function 0 around.
> >
> > I suppose the guest will remove all functions of a device once you
> > attempt to hot-unplug a fun
Philipp,
Thanks for debugging this issue. We'll be fowarding the fix
for inclusion in the official 2.6.32 tree.
On Mon, Sep 05, 2011 at 04:06:57PM +0200, Philipp Hahn wrote:
> Hello,
>
> (cc:-ing lost of people who reported similar bugs on kvm-devel)
> > Changing clock in KVM host may cause VM
On Mon, Sep 12, 2011 at 07:21:48AM -0300, Marcelo Tosatti wrote:
> > We could, for example, keep a stub function 0 around.
>
> I suppose the guest will remove all functions of a device once you
> attempt to hot-unplug a function.
>
> What is the problem with adding more PCI buses, instead of mult
> -Original Message-
> From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-
> ow...@vger.kernel.org] On Behalf Of Kun Wang
> Sent: Tuesday, August 30, 2011 7:32 PM
> To: Stuart Yoder
> Cc: Kun Wang; kvm-...@vger.kernel.org; kvm@vger.kernel.org; Wood Scott-
> B07421; Alexander Graf
> Subject
Certain guests, specifically RTOSes, request faster periodic timers than
what we allow by default. Add a module parameter to adjust the limit for
non-standard setups. Also add a rate-limited warning in case the guest
requested more.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/lapic.c | 15 +
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Joerg Roedel
> Sent: Thursday, September 08, 2011 12:49 AM
> To: Greg KH
> Cc: Joerg Roedel; io...@lists.linux-foundation.org; Alex Williamson; Ohad
> Ben-Cohen; David Woodhouse; David
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Joerg Roedel
> Sent: Wednesday, September 07, 2011 9:12 PM
> To: io...@lists.linux-foundation.org
> Cc: Greg Kroah-Hartman; Alex Williamson; Ohad Ben-Cohen; David Woodhouse;
> David Br
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Joerg Roedel
> Sent: Thursday, September 08, 2011 2:12 PM
> To: Greg KH
> Cc: Joerg Roedel; io...@lists.linux-foundation.org; Alex Williamson; Ohad
> Ben-Cohen; David Woodhouse; David
On Tue, 2011-08-30 at 09:15 -0500, Stuart Yoder wrote:
> Also, note-- we (Freescale) do have a patchset coming soon for the e500mc
> which is a 2.06 embedded 32-bit CPU with category E.HV.We've had this
> running for a while and are close to finishing some cleanup before posting
> upstream. W
On Sun, Sep 11, 2011 at 09:51:06PM +0300, Michael S. Tsirkin wrote:
> On Sun, Sep 11, 2011 at 12:01:49PM -0300, Marcelo Tosatti wrote:
> > On Sun, Sep 11, 2011 at 12:23:57PM +0300, Michael S. Tsirkin wrote:
> > > On Fri, Sep 09, 2011 at 03:34:26PM -0300, Marcelo Tosatti wrote:
> > > > > > something
The use of printk_ratelimit is discouraged, replace it with
pr*_ratelimited or __ratelimit. While at it, convert remaining
guest-triggerable printks to rate-limited variants.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/i8259.c | 15 ---
arch/x86/kvm/mmu_audit.c |6 +++---
ar
Convert remaining printks that the guest can trigger to apic_printk.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/lapic.c | 19 +--
1 files changed, 9 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 52645f2..4b53b81 100644
--- a/arch
This avoids that events causing the vmexit are recorded before the
actual exit reason.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/svm.c |4 ++--
arch/x86/kvm/vmx.c |3 +--
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 8277f32
43 matches
Mail list logo