Hi Anthony, Stefan & QEMU folks,
So during the process of separating out the patches from Zhi's
vhost-scsi tree this evening, I managed to squash everything down to
nine nicely reviewable patches that apply against the current
qemu.git/master:
Nicholas Bellinger (1):
virtio-scsi: Set max_target
On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
> As it was discussed recently, there's currently no way for the guest to notify
> the host about panics. Further more, there's no reasonable way to notify the
> host of other critical events such as an OOM kill.
>
> This short patch ser
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 23, 2012 10:00 PM
> To: Bhushan Bharat-R65777
> Cc: Wood Scott-B07421; kvm-...@vger.kernel.org; kvm@vger.kernel.org;
> ag...@suse.de
> Subject: Re: [PATCH 2/2 v5] KVM: PPC: booke: Add watchdog emulation
>
> On 07/23/2012
On 2012-07-24 09:42, Nicholas A. Bellinger wrote:
> Hi Anthony, Stefan & QEMU folks,
>
> So during the process of separating out the patches from Zhi's
> vhost-scsi tree this evening, I managed to squash everything down to
> nine nicely reviewable patches that apply against the current
> qemu.git/
On 07/24/2012 07:55 AM, Rusty Russell wrote:
On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin wrote:
As it was discussed recently, there's currently no way for the guest to notify
the host about panics. Further more, there's no reasonable way to notify the
host of other critical events such as a
On 07/23/2012 08:58 PM, Peter Maydell wrote:
> On 23 July 2012 15:30, Avi Kivity wrote:
>> But I was only joking. Nested virtualization is interesting technically
>> but so far I haven't seen any huge or even small uptake.
>
> Yes; that (as I understand it) is why it wasn't an expected use
> cas
On 24 July 2012 09:50, Avi Kivity wrote:
> On 07/23/2012 08:58 PM, Peter Maydell wrote:
>> The other related thing that
>> might be surprising for x86-background people is that being
>> able to present the guest with a virtual CPU that looks like
>> a pre-virtualization CPU (eg the A9) isn't reall
On 07/23/2012 06:19 PM, Peter Maydell wrote:
> On 23 July 2012 13:26, Avi Kivity wrote:
>> On 07/21/2012 11:54 AM, Peter Maydell wrote:
>>> The reason I want to get rid of common-code uses of kvm_irqchip_in_kernel()
>>> is because I think they're all similar to this -- the common code is
>>> using
From: Raghavendra K T
Thanks Alex for KVM_HC_FEATURES inputs and Jan for VAPIC_POLL_IRQ,
and Peter (HPA) for suggesting hypercall ABI addition.
Signed-off-by: Raghavendra K T
---
Please have a closer look at Hypercall ABI newly added
Changes since last post:
- Added hypercall ABI (Peter)
- m
On 2012-07-24 10:54, Peter Maydell wrote:
> On 24 July 2012 09:50, Avi Kivity wrote:
>> On 07/23/2012 08:58 PM, Peter Maydell wrote:
>>> The other related thing that
>>> might be surprising for x86-background people is that being
>>> able to present the guest with a virtual CPU that looks like
>>>
On Mon, 2012-07-23 at 10:12 -0700, Tejun Heo wrote:
> Hello,
>
> On Sun, Jul 22, 2012 at 04:46:54PM -0400, Andy Walls wrote:
> > Hmmm, I didn't know about the constraint about 'known to be alive' in
> > the other email I just sent.
> >
> > That might make calling flush_kthread_work() hard for a u
On Tue, Jul 24, 2012 at 8:57 AM, Jan Kiszka wrote:
> On 2012-07-24 09:42, Nicholas A. Bellinger wrote:
>> Hi Anthony, Stefan & QEMU folks,
>>
>> So during the process of separating out the patches from Zhi's
>> vhost-scsi tree this evening, I managed to squash everything down to
>> nine nicely rev
On 2012-07-24 14:05, Stefan Hajnoczi wrote:
> On Tue, Jul 24, 2012 at 8:57 AM, Jan Kiszka wrote:
>> On 2012-07-24 09:42, Nicholas A. Bellinger wrote:
>>> Hi Anthony, Stefan & QEMU folks,
>>>
>>> So during the process of separating out the patches from Zhi's
>>> vhost-scsi tree this evening, I mana
On 07/24/2012 10:53 AM, Raghavendra K T wrote:
From: Raghavendra K T
Thanks Alex for KVM_HC_FEATURES inputs and Jan for VAPIC_POLL_IRQ,
and Peter (HPA) for suggesting hypercall ABI addition.
Signed-off-by: Raghavendra K T
---
Please have a closer look at Hypercall ABI newly added
Changes sin
On 07/24/2012 06:55 AM, Rusty Russell wrote:> On Mon, 23 Jul 2012 22:32:39
+0200, Sasha Levin wrote:
>> As it was discussed recently, there's currently no way for the guest to
>> notify
>> the host about panics. Further more, there's no reasonable way to notify the
>> host of other critical even
On 07/23/2012 02:06 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
if=ahci
Alex
--
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
On 07/24/2012 09:44 AM, Gleb Natapov wrote:
> On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
>> As it was discussed recently, there's currently no way for the guest to
>> notify
>> the host about panics. Further more, there's no reasonable way to notify the
>> host of other critical
On Tue, Jul 24, 2012 at 02:26:33PM +0200, Sasha Levin wrote:
> On 07/24/2012 09:44 AM, Gleb Natapov wrote:
> > On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
> >> As it was discussed recently, there's currently no way for the guest to
> >> notify
> >> the host about panics. Further m
On 07/24/2012 10:26 AM, Dor Laor wrote:
> On 07/24/2012 07:55 AM, Rusty Russell wrote:
>> On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin
>> wrote:
>>> As it was discussed recently, there's currently no way for the guest to
>>> notify
>>> the host about panics. Further more, there's no reasonabl
On 07/24/2012 02:28 PM, Gleb Natapov wrote:
> On Tue, Jul 24, 2012 at 02:26:33PM +0200, Sasha Levin wrote:
>> On 07/24/2012 09:44 AM, Gleb Natapov wrote:
>>> On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
As it was discussed recently, there's currently no way for the guest to
>>
On Tue, Jul 24, 2012 at 02:31:25PM +0200, Sasha Levin wrote:
> On 07/24/2012 02:28 PM, Gleb Natapov wrote:
> > On Tue, Jul 24, 2012 at 02:26:33PM +0200, Sasha Levin wrote:
> >> On 07/24/2012 09:44 AM, Gleb Natapov wrote:
> >>> On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
> As i
Ping. Is some additional work expected from me before this is applied?
On Tue, Jul 17, 2012 at 02:59:11PM +0300, Gleb Natapov wrote:
> After commit 242ec97c358256 PIT interrupts are no longer delivered after
> PIC reset. It happens because PIT injects interrupt only if previous one
> was acked, bu
On Tue, Jul 3, 2012 at 9:50 PM, Marcelo Tosatti wrote:
> On Tue, Jul 03, 2012 at 04:59:54AM -0400, Christoffer Dall wrote:
>> Handle KVM_IRQ_LINE and KVM_IRQ_LINE_STATUS in the generic
>> kvm_vm_ioctl() function and call into kvm_vm_ioctl_irq_line().
>>
>> Signed-off-by: Christoffer Dall
>> ---
>
On Tue, Jul 24, 2012 at 03:35:14PM +0300, Gleb Natapov wrote:
> Ping. Is some additional work expected from me before this is applied?
Still not clear to me why its safe to skip kvm_apic_accept_pic_intr check
before calling ack notifier.
> On Tue, Jul 17, 2012 at 02:59:11PM +0300, Gleb Natapov
On 07/24/2012 03:04 AM, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Alexander Graf [mailto:ag...@suse.de]
Sent: Monday, July 23, 2012 11:12 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; kvm-...@vger.kernel.org; kvm@vger.kernel.org
Subject: Re: [PATCH v2] booke: Added ONE
On 07/24/2012 03:30 PM, Sasha Levin wrote:
On 07/24/2012 10:26 AM, Dor Laor wrote:
On 07/24/2012 07:55 AM, Rusty Russell wrote:
On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin wrote:
As it was discussed recently, there's currently no way for the guest to notify
the host about panics. Further
Handle KVM_IRQ_LINE and KVM_IRQ_LINE_STATUS in the generic
kvm_vm_ioctl() function and call into kvm_vm_ioctl_irq_line().
This is even more relevant when KVM/ARM also uses this ioctl.
Signed-off-by: Christoffer Dall
---
arch/ia64/kvm/kvm-ia64.c | 33 ++---
arch/x86
On 07/24/2012 02:46 PM, Dor Laor wrote:
> On 07/24/2012 03:30 PM, Sasha Levin wrote:
>> On 07/24/2012 10:26 AM, Dor Laor wrote:
>>> On 07/24/2012 07:55 AM, Rusty Russell wrote:
On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin
wrote:
> As it was discussed recently, there's currently n
On Tue, Jul 24, 2012 at 09:40:26AM -0300, Marcelo Tosatti wrote:
>
> On Tue, Jul 24, 2012 at 03:35:14PM +0300, Gleb Natapov wrote:
> > Ping. Is some additional work expected from me before this is applied?
>
> Still not clear to me why its safe to skip kvm_apic_accept_pic_intr check
> before call
On 07/24/2012 05:43 PM, Alexander Graf wrote:
On 07/24/2012 10:53 AM, Raghavendra K T wrote:
From: Raghavendra K T
Thanks Alex for KVM_HC_FEATURES inputs and Jan for VAPIC_POLL_IRQ,
and Peter (HPA) for suggesting hypercall ABI addition.
Signed-off-by: Raghavendra K T
---
Please have a closer
> > +struct kvmppc_debug_reg {
> > +#ifdef CONFIG_BOOKE
> > + u32 dbcr0;
> > + u32 dbcr1;
> > + u32 dbcr2;
> > +#ifdef CONFIG_KVM_E500MC
> > + u32 dbcr4;
> > +#endif
> > + u64 iac[KVMPPC_MAX_IAC];
> > + u64 dac[KVMPPC_MAX_D
On Tue, Jul 24, 2012 at 01:26:20AM +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> As requested by Anthony, here is a patch against target-pending/for-next-merge
> to expose an ABI version to userspace via a new VHOST_SCSI_GET_ABI_VERSION
> ioctl operation.
>
> As mentioned in
On 07/24/2012 03:26 PM, Bhushan Bharat-R65777 wrote:
+struct kvmppc_debug_reg {
+#ifdef CONFIG_BOOKE
+ u32 dbcr0;
+ u32 dbcr1;
+ u32 dbcr2;
+#ifdef CONFIG_KVM_E500MC
+ u32 dbcr4;
+#endif
+ u64 iac[KVMPPC_MAX_IAC];
+ u64 dac[KVMPPC_MAX_DAC];
+#endif
+};
Is ther
Hi
Minutes of Today call.
ahci: agraf
- how to enable it?
* today is too difficult (alex)
* get it to work as everything else (markus)
And big discussion ensued. Markus & alex will reply with details.
No agreement, and too subtle for me to resume perfectly.
* cdrom still not worki
IAC/DAC are defined as 32 bit while they are 64 bit wide. So ONE_REG
interface is added to set/get them.
Signed-off-by: Bharat Bhushan
---
v3:
- IAC3/4 defined on non-fsl booke
- kvmppc_debug_reg renamed to kvmppc_booke_debug_reg
v2:
- Using copy_to/from_user() apis.
arch/powerpc/include/as
Ok, this caused conflicts with the s390 and ppc trees. I think I fixed
them correctly, but the respective arch people really should take a
look.
Linus
On Mon, Jul 23, 2012 at 2:12 AM, Avi Kivity wrote:
> Linus, please pull from the repo and tag at:
>
> git://git.kernel.org/pu
On Tue, 2012-07-24 at 09:57 +0200, Jan Kiszka wrote:
> On 2012-07-24 09:42, Nicholas A. Bellinger wrote:
> > Hi Anthony, Stefan & QEMU folks,
> >
> > However, thus far I've not been able to get virtio-scsi <-> tcm_vhost
> > I/O to actually work against the latest qemu.git/master..
> >
> > So
v7:
Just a minor change from v6 to fix locking. In v6 we called
f_op->poll under eoifds.lock to install the eventfd waitqueue
function. This creates a eoifds.lock --> ctx->wqh lock ordering.
When our wakeup function gets called it's under ctx->wqh and
acquires eoifds.lock. Badness. To fix this
In order to inject a level interrupt from an external source using an
irqfd, we need to allocate a new irq_source_id. This allows us to
assert and (later) de-assert an interrupt line independently from
users of KVM_IRQ_LINE and avoid lost interrupts.
We also add what may appear like a bit of exce
This new ioctl enables an eventfd to be triggered when an EOI is
written for a specified irqchip pin. The first user of this will
be external device assignment through VFIO, using a level irqfd
for asserting a PCI INTx interrupt and this interface for de-assert
and notification once the interrupt
On Mon, 2012-07-23 at 18:56 -0700, Greg Kroah-Hartman wrote:
> On Tue, Jul 24, 2012 at 01:26:20AM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > As requested by Anthony, here is a patch against
> > target-pending/for-next-merge
> > to expose an ABI version to userspace
On Tue, 2012-07-24 at 13:20 -0700, Nicholas A. Bellinger wrote:
> On Tue, 2012-07-24 at 09:57 +0200, Jan Kiszka wrote:
> > On 2012-07-24 09:42, Nicholas A. Bellinger wrote:
> > > Hi Anthony, Stefan & QEMU folks,
> > >
>
>
>
> > > However, thus far I've not been able to get virtio-scsi <-> tcm_v
On 07/24/2012 02:45 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 10:00 PM
>> To: Bhushan Bharat-R65777
>> Cc: Wood Scott-B07421; kvm-...@vger.kernel.org; kvm@vger.kernel.org;
>> ag...@suse.de
>> Subject: Re: [PATCH 2/
From: Nicholas Bellinger
Hi Anthony + QEMU storage folks,
The following is a reviewable RFC series of vhost-scsi against yesterday's
QEMU.git/master @ commit 401a66357d.
The series is available directly from:
git://git.kernel.org/pub/scm/virt/kvm/nab/qemu-kvm.git vhost-scsi-merge
It contain
From: Stefan Hajnoczi
Normally host notifiers are only used together with vhost-net in KVM
mode. It is occassionally useful to use vhost with TCG mode, mainly for
testing and development. This isn't hard to achieve, simply fall back
to notifying the host notifier manually from qemu if KVM mode
From: Stefan Hajnoczi
Event notifiers that have not had the event_notifier_init() function
called on them are invalid. The event_notifier_valid() function checks
whether or not an event notifier is valild. This can be used to check
whether a notifier is in use or not.
It sometimes useful to no
From: Stefan Hajnoczi
For sanity assert that event notification succeeds.
Signed-off-by: Stefan Hajnoczi
Cc: Anthony Liguori
Cc: Paolo Bonzini
Signed-off-by: Nicholas Bellinger
---
hw/virtio-pci.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/hw/virtio-pci.c b
From: Stefan Hajnoczi
A vhost-scsi device must be bound to a tcm_vhost target port. This will
be done by issuing an ioctl to the device with the wwpn and tgpt. This
patch adds these properties to the virtio-scsi-pci device:
qemu -device virtio-scsi-pci,wwpn=$TARGET_WWN,tgpt=$TPGT
Future pat
From: Stefan Hajnoczi
The path to /dev/vhost-net is currently hardcoded in vhost_dev_init().
This needs to be changed so that /dev/vhost-scsi can be used. Pass in
the device path instead of hardcoding it.
Signed-off-by: Stefan Hajnoczi
Cc: Paolo Bonzini
Cc: Michael S. Tsirkin
Signed-off-by:
From: Stefan Hajnoczi
Begin adding vhost support by opening /dev/vhost-scsi.
(v2: Drop legacy ->vhost_vqs[] usage)
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Signed-off-by: Nicholas Bellinger
---
hw/virtio-scsi.c | 12
From: Stefan Hajnoczi
This patch starts and stops vhost as the virtio device transitions
through its status phases. Vhost can only be started once the guest
reports its driver has successfully initialized, which means the
virtqueues have been set up by the guest.
(v2: Squash virtio-scsi: use th
From: Nicholas Bellinger
This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation
to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID
instance) when connected to individual tcm_vhost endpoints.
This ensures that virtio-scsi LLD only attempts to scan tar
From: Stefan Hajnoczi
This patch adds a new type of host device that drives the vhost_scsi
device. The syntax to add vhost-scsi is:
qemu -vhost-scsi id=vhost-scsi0,wwpn=...,tpgt=123
The virtio-scsi emulated device will make use of vhost-scsi to process
virtio-scsi requests inside the kernel
On Tue, 2012-07-24 at 12:04 -0700, Linus Torvalds wrote:
> Ok, this caused conflicts with the s390 and ppc trees. I think I fixed
> them correctly, but the respective arch people really should take a
> look.
A quick peek at the merge commit looks allright, but Alex mentioned that
there's some more
After merging the register type check patches from Ben's tree, the
hv enabled booke implementation ceased to compile.
This patch fixes things up so everyone's happy again.
Signed-off-by: Alexander Graf
---
arch/powerpc/kvm/bookehv_interrupts.S | 77 +
1 files c
On Wed, 25 Jul 2012 08:38:36 +1000 Benjamin Herrenschmidt
wrote:
>
> On Tue, 2012-07-24 at 12:04 -0700, Linus Torvalds wrote:
> > Ok, this caused conflicts with the s390 and ppc trees. I think I fixed
> > them correctly, but the respective arch people really should take a
> > look.
>
> A quick p
On Wed, Jul 25, 2012 at 6:33 AM, Nicholas A. Bellinger
wrote:
> From: Nicholas Bellinger
>
> Hi Anthony + QEMU storage folks,
>
> The following is a reviewable RFC series of vhost-scsi against yesterday's
> QEMU.git/master @ commit 401a66357d.
>
> The series is available directly from:
>
> git:
On Tue, 24 Jul 2012 15:01:59 +0200, Sasha Levin wrote:
> virtio on it's own was introduced to help solve the fragmentation
> around virtualized devices, so I don't think that the main purpose of
> doing virtio drivers is due to any performance benefits virtio may
> provide.
There's one argument i
On Thu, 05 Jul 2012 09:02:23 +0200, Sasha Levin wrote:
> On Thu, 2012-07-05 at 08:47 +0200, Paolo Bonzini wrote:
> > Il 04/07/2012 23:11, Sasha Levin ha scritto:
> > > There are two things going on here:
> > > 1. Rename VIRTIO_BLK_F_FLUSH to VIRTIO_BLK_F_WCE
> > > 2. Add a new VIRTIO_BLK_F_CONFI
refer to orignal plan posted by Marcelo Tosatti,
http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg04315.html
These patches protect DeviceState's rd from reclaimer. It is neccessary
when no qemu_global_lock protects between them.
--
To unsubscribe from this list: send the line "unsubscribe k
From: Liu Ping Fan
When guest confirm the removal of device, we should
--unmap from MemoryRegion view
--isolated from device tree view
Signed-off-by: Liu Ping Fan
---
hw/acpi_piix4.c |4 ++--
hw/qdev.c | 28
hw/qdev.h |3 ++-
3 files changed,
From: Liu Ping Fan
acquire device's refcnt with qemu_device_tree_mutex rwlock, so we
can safely handle it when mmio dispatch.
If in radix-tree, leaf is subpage, then move further step to acquire
opaque which is the type --DeiveState.
Signed-off-by: Liu Ping Fan
---
exec.c | 38 +++
From: Liu Ping Fan
rwlock:
qemu_device_tree_mutex
rd side:
--device_del(destruction of device will be postphoned until unplug
ack from guest),
--pci hot-unplug
--iteration (qdev_reset_all)
wr side:
--device_add
Signed-off-by: Liu Ping Fan
---
hw/pci-hotplug.c |4
hw/q
From: Liu Ping Fan
iohandler/bh/timer may use DeviceState when its refcnt=0,
postpone the reclaimer till they have done with it.
Signed-off-by: Liu Ping Fan
---
include/qemu/object.h |2 +-
main-loop.c |4
main-loop.h |2 ++
qemu-tool.c |4 +++
From: Liu Ping Fan
Signed-off-by: Liu Ping Fan
---
hw/e1000.c | 15 +--
1 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/hw/e1000.c b/hw/e1000.c
index 4573f13..4c1e141 100644
--- a/hw/e1000.c
+++ b/hw/e1000.c
@@ -1192,6 +1192,18 @@ e1000_cleanup(VLANClientState *nc)
This patch adds the watchdog emulation in KVM. The watchdog
emulation is enabled by KVM_ENABLE_CAP(KVM_CAP_PPC_BOOKE_WATCHDOG) ioctl.
The kernel timer are used for watchdog emulation and emulates
h/w watchdog state machine. On watchdog timer expiry, it exit to QEMU
if TCR.WRC is non ZERO. QEMU can
Il 25/07/2012 00:33, Nicholas A. Bellinger ha scritto:
> From: Stefan Hajnoczi
>
> Normally host notifiers are only used together with vhost-net in KVM
> mode. It is occassionally useful to use vhost with TCG mode, mainly for
> testing and development. This isn't hard to achieve, simply fall ba
Il 25/07/2012 00:33, Nicholas A. Bellinger ha scritto:
> +int event_notifier_notify(EventNotifier *e)
> +{
> +uint64_t value = 1;
> +int r;
> +
> +assert(event_notifier_valid(e));
> +r = write(e->fd, &value, sizeof(value));
> +if (r < 0) {
> +return -errno;
> +}
> +
Il 25/07/2012 00:34, Nicholas A. Bellinger ha scritto:
> From: Stefan Hajnoczi
>
> This patch adds a new type of host device that drives the vhost_scsi
> device. The syntax to add vhost-scsi is:
>
> qemu -vhost-scsi id=vhost-scsi0,wwpn=...,tpgt=123
>
> The virtio-scsi emulated device will ma
69 matches
Mail list logo
