On Fri, Mar 08, 2013 at 10:21:41AM +0800, Asias He wrote:
> Changes in v2:
> - Remove code duplication in tcm_vhost_{hotplug,hotunplug}
> - Fix racing of vs_events_nr
> - Add flush fix patch to this series
>
> Asias He (6):
> tcm_vhost: Add missed lock in vhost_scsi_clear_endpoint()
> tcm_vhos
On Thu, Mar 07, 2013 at 12:57:55PM +0100, Wolfgang Hennerbichler wrote:
> I'm running a virtual machine with the following command:
>
> LC_ALL=C
> PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 4096 -smp
> 2,sockets=
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
>
> Could you please (in a quick and drafty way) try and see if setting the IRQ
> arch (using enable_cap) after the vcpu got created would work for you?
>
> That enable_cap would then have to loop through all devices and notify irq
Am 08.03.2013 um 11:37 schrieb Paul Mackerras :
> On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
>>
>> Could you please (in a quick and drafty way) try and see if setting the IRQ
>> arch (using enable_cap) after the vcpu got created would work for you?
>>
>> That enable_cap w
On Fri, Mar 08, 2013 at 04:12:41AM +0100, Marc Zyngier wrote:
> On Thu, 7 Mar 2013 16:09:00 -0300, Marcelo Tosatti
> wrote:
> > On Thu, Mar 07, 2013 at 07:57:23AM +0100, Marc Zyngier wrote:
> >> On Wed, 6 Mar 2013 20:40:00 -0800, Christoffer Dall
> >>
> >> wrote:
> >> > On Wed, Mar 6, 2013 at 7:5
On Thu, Mar 07, 2013 at 10:56:34PM -0500, l...@mymail.vcu.edu wrote:
> As we have known, in KVM full virtualization, guest VM is running in
> non-root mode and KVM is running in root mode. While, in non-root
> mode, guest kernel is running in Ring 0 and Apps are running in Ring
> 3. However, what
On 19.02.2013, at 05:13, Scott Wood wrote:
> The existing check handles the case where we've migrated to a different
> core than we last ran on, but it doesn't handle the case where we're
> still on the same cpu we last ran on, but some other vcpu has run on
> this cpu in the meantime.
>
> Signe
On 14.02.2013, at 06:37, Scott Wood wrote:
> Scott Wood (3):
> kvm/ppc/e500: h2g_tlb1_rmap: esel 0 is valid
> kvm/ppc/e500: g2h_tlb1_map: clear old bit before setting new bit
> kvm/ppc/e500: eliminate tlb_refs
>
> arch/powerpc/kvm/e500.h | 24 ---
> arch/powerpc/kvm/e500_mmu
* Yang Zhang wrote:
> diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c
> index 6e03b0d..2329a54 100644
> --- a/arch/x86/kernel/irqinit.c
> +++ b/arch/x86/kernel/irqinit.c
> @@ -205,6 +205,10 @@ static void __init apic_intr_init(void)
>
> /* IPI for X86 platform specific
On Fri, Mar 08, 2013 at 02:26:25PM +0100, Ingo Molnar wrote:
>
> * Yang Zhang wrote:
>
> > diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c
> > index 6e03b0d..2329a54 100644
> > --- a/arch/x86/kernel/irqinit.c
> > +++ b/arch/x86/kernel/irqinit.c
> > @@ -205,6 +205,10 @@ static
* Gleb Natapov wrote:
> On Fri, Mar 08, 2013 at 02:26:25PM +0100, Ingo Molnar wrote:
> >
> > * Yang Zhang wrote:
> >
> > > diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c
> > > index 6e03b0d..2329a54 100644
> > > --- a/arch/x86/kernel/irqinit.c
> > > +++ b/arch/x86/kernel/i
Ingo Molnar wrote on 2013-03-08:
>
> * Gleb Natapov wrote:
>
>> On Fri, Mar 08, 2013 at 02:26:25PM +0100, Ingo Molnar wrote:
>>>
>>> * Yang Zhang wrote:
>>>
diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c
index 6e03b0d..2329a54 100644
--- a/arch/x86/kernel/ir
On Fri, Mar 08, 2013 at 03:05:45PM +0100, Ingo Molnar wrote:
>
> * Gleb Natapov wrote:
>
> > On Fri, Mar 08, 2013 at 02:26:25PM +0100, Ingo Molnar wrote:
> > >
> > > * Yang Zhang wrote:
> > >
> > > > diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c
> > > > index 6e03b0d..232
On 03/08/2013 06:42 AM, Gleb Natapov wrote:
On Thu, Mar 07, 2013 at 10:56:34PM -0500, l...@mymail.vcu.edu wrote:
As we have known, in KVM full virtualization, guest VM is running in
non-root mode and KVM is running in root mode. While, in non-root
mode, guest kernel is running in Ring 0 and Apps
On Fri, 2013-03-08 at 14:24 +0800, Jason Wang wrote:
> Hello all:
>
> I meet an issue when testing multiqueue virtio-net. When I testing guest
> small packets stream sending performance with netperf. I find an
> regression of multiqueue. When I run 2 sessions of TCP_STREAM test with
> 1024 byte fr
* Gleb Natapov wrote:
> On Fri, Mar 08, 2013 at 03:05:45PM +0100, Ingo Molnar wrote:
> >
> > * Gleb Natapov wrote:
> >
> > > On Fri, Mar 08, 2013 at 02:26:25PM +0100, Ingo Molnar wrote:
> > > >
> > > > * Yang Zhang wrote:
> > > >
> > > > > diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/
Well, the point is : if your app does write(1024) bytes, thats probably
because it wants small packets from the very beginning. (See the TCP
PUSH flag ?)
I think that raises the question of whether or not Jason was setting the
test-specific -D option on his TCP_STREAM tests, to have netperf
On 03/04/2013 02:33 AM, Frank Bonnet wrote:
Hello
Not sure if this is the right list. You might get more help on the
qemu-devel list.
I'm in trouble with a guest host that is not living on the same subnet
than the hypervisor that I would like to connect to my LAN through
802.1q VLAN ( ubu
On Thu, Mar 7, 2013 at 7:12 PM, Marc Zyngier wrote:
> On Thu, 7 Mar 2013 16:09:00 -0300, Marcelo Tosatti
> wrote:
>> On Thu, Mar 07, 2013 at 07:57:23AM +0100, Marc Zyngier wrote:
>>> On Wed, 6 Mar 2013 20:40:00 -0800, Christoffer Dall
>>>
>>> wrote:
>>> > On Wed, Mar 6, 2013 at 7:54 PM, Marc Zyn
On Fri, Mar 08, 2013 at 09:23:20AM +0800, Yang Zhang wrote:
> From: Yang Zhang
>
> Only deliver the posted interrupt when target vcpu is running
> and there is no previous interrupt pending in pir.
>
> Signed-off-by: Yang Zhang
> +static bool vmx_deliver_posted_interrupt(struct kvm_vcpu *vcpu,
On Fri, Mar 08, 2013 at 09:23:21AM +0800, Yang Zhang wrote:
> From: Yang Zhang
>
> If posted interrupt is avaliable, then uses it to inject virtual
> interrupt to guest.
>
> Signed-off-by: Yang Zhang
> ---
> arch/x86/kvm/irq.c |2 +-
> arch/x86/kvm/lapic.c | 16 +---
> arch
The existing check handles the case where we've migrated to a different
core than we last ran on, but it doesn't handle the case where we're
still on the same cpu we last ran on, but some other vcpu has run on
this cpu in the meantime.
Without this, guest segfaults (and other misbehavior) have bee
On 08.03.2013, at 21:25, Scott Wood wrote:
> The existing check handles the case where we've migrated to a different
> core than we last ran on, but it doesn't handle the case where we're
> still on the same cpu we last ran on, but some other vcpu has run on
> this cpu in the meantime.
>
> Witho
Marcelo Tosatti wrote on 2013-03-09:
> On Fri, Mar 08, 2013 at 09:23:20AM +0800, Yang Zhang wrote:
>> From: Yang Zhang
>>
>> Only deliver the posted interrupt when target vcpu is running
>> and there is no previous interrupt pending in pir.
>>
>> Signed-off-by: Yang Zhang
>>
>> +static bool vm
Marcelo Tosatti wrote on 2013-03-09:
> On Fri, Mar 08, 2013 at 09:23:21AM +0800, Yang Zhang wrote:
>> From: Yang Zhang
>>
>> If posted interrupt is avaliable, then uses it to inject virtual
>> interrupt to guest.
>>
>> Signed-off-by: Yang Zhang
>> ---
>> arch/x86/kvm/irq.c |2 +-
>> arch
On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
>
>
> Am 08.03.2013 um 11:37 schrieb Paul Mackerras :
>
> > I have
> > used the first argument (cap->args[0]) to specify which interrupt
> > controller you want to connect the vcpu to.
>
> Ah, nice idea. So you basically make the v
After receiving an INIT signal (either via the local APIC, or through
KVM_SET_MP_STATE), the bootstrap processor should reset immediately
and start execution at 0xfff0. Also, SIPIs have no effect on the
bootstrap processor. However, KVM currently does not differentiate
between the BSP and APs
This is a follow up to the series I posted earlier this week to
support CPU soft reset. It is a no-op without that series, but
it can be applied independently.
The combined series is available at branch x86-soft-reset of
my github repository (git://github.com/bonzini/qemu.git). With
this series
The next patch will call a ioctl from kvm_arch_process_async_events.
Trap errors and abort the program if one comes.
Signed-off-by: Paolo Bonzini
---
kvm-all.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/kvm-all.c b/kvm-all.c
index 4decfdc..bc1534c 100644
--- a/kvm
CPU_INTERRUPT_INIT can also be generated if you have an internal APIC,
since the keyboard controller and the southbridge can also pulse the
CPU's INIT# pin.
Exit the VCPU is one is received, and process it by changing the
mp_state to KVM_MP_STATE_INIT_RECEIVED.
Signed-off-by: Paolo Bonzini
---
- Added vfio_device_get_from_dev() as wrapper to get
reference to vfio_device from struct device.
- Added vfio_device_data() as a wrapper to get device_data from
vfio_device.
Signed-off-by: Vijay Mohan Pandarathil
---
drivers/vfio/vfio.c | 30 +++
- Create eventfd per vfio device assigned to a guest and register an
event handler
- This fd is passed to the vfio_pci driver through the SET_IRQ ioctl
- When the device encounters an error, the eventfd is signalled
and the qemu eventfd handler gets inv
Add support for error containment when a VFIO device assigned to a KVM
guest encounters an error. This is for PCIe devices/drivers that support AER
functionality. When the host OS is notified of an error in a device either
through the firmware first approach or through an interrupt handled by the A
- New VFIO_SET_IRQ ioctl option to pass the eventfd that is signaled
when
an error occurs in the vfio_pci_device
- Register pci_error_handler for the vfio_pci driver
- When the device encounters an error, the error handler registered by
the vfio_pci dr
34 matches
Mail list logo
