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 an OOM kill.
I clearly missed the discussi
On 07/23/2012 10:03 PM, Xiao Guangrong wrote:
> Currently, kvm allocates some pages and use then as error indicators,
> it wastes memory and is not good for scalability.
>
> In this patchset, we introduce some error code instead of the pages to
> indicate the error conditions.
>
Sorry for the no
From: Nicholas Bellinger
Rename the main IOCTL structure to vhost_scsi_target so that
it makes a little more sense than vhost_vring_target.
As requested by MST.
Reported-by: Michael S. Tsirkin
Cc: Stefan Hajnoczi
Cc: Anthony Liguori
Cc: Paolo Bonzini
Cc: Zhi Yong Wu
Signed-off-by: Nicholas
From: Nicholas Bellinger
This patch adds support in vhost-scsi QEMU userspace code to check the
running tcm_vhost ABI version using VHOST_SCSI_GET_ABI_VERSION.
This series selects VHOST_SCSI_ABI_VERSION=1 for current code, and
requires the pre-requsite tcm_vhost patch to expose an ABI version nu
From: Nicholas Bellinger
Hi Anthony,
Here are the two patches against Zhi's vhost-scsi tree to check for
a supported version (VHOST_SCSI_ABI_VERSION=1) that's now exposed via
the tcm_vhost ioctl.
Please have a look and let me know if this is what you had in mind.
Thanks!
Nicholas Bellinger (2
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 the comment, ABI Rev 0 is for pre 2012 out-of-tree code, and
ABI Rev 1 (the current
> -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_REG interface for IAC/DAC debug
> register
On Fri, Jul 20, 2012 at 10:50:11AM -0600, Bruce Rogers wrote:
> When a guest is migrated, a time offset is generated in order to
> maintain the correct kvmclock based time for the guest. Detect when
> all kvmclock time pages are deleted so that the kvmclock offset can
> be safely reset to zero.
>
On Fri, Jul 20, 2012 at 10:44:24AM -0600, Bruce Rogers wrote:
> When a guest migrates to a new host, the system time difference from the
> previous host is used in the updates to the kvmclock system time visible
> to the guest, resulting in a continuation of correct kvmclock based guest
> timekeepi
On Fri, 2012-07-20 at 10:33 -0600, Alex Williamson wrote:
> v6:
>
> So we're back to just the first two patches, unfortunately the
> diffstat got bigger though. The reason for that is that I discovered
> we don't do anything on release of an eoifd. We cleanup if the kvm
> vm is released, but we'
This patch supports the new virtio-notifier driver.
When the guest experiences a panic or an OOM, it will notify the host and
the host will notify the user of the event.
We also ping echo packets every second to the guest to see if it's still
alive and well, I haven't actually taken care of the c
[TODO: Find a better name]
virtio-notifier is a new driver which provides guests the ability to report
critical events such as a panic or OOM to the host.
The driver also provides an "echo" channel which is primed with a buffer when
the driver is initialized, and allows the host to "ping" the gue
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 series introduces a new device named virtio-notifier which
does two simple
On Mon, 2012-07-23 at 08:16 -0700, Greg KH wrote:
> On Sun, Jul 22, 2012 at 02:44:23PM -0700, Nicholas A. Bellinger wrote:
> > So Linus has merged target-pending/for-next this afternoon, so now we
> > are just waiting on net-next to hit mainline with the vhost patches
> > already ACK'ed by MST. Ho
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
case for the architecture extensions. The other related th
On 2012-07-23 19:41, Peter Maydell wrote:
> On 23 July 2012 17:55, Jan Kiszka wrote:
>> On 2012-07-23 17:19, Peter Maydell wrote:
>>> OK, let's see if we can get some agreement about naming here.
>>>
>>> First, some test-functions I think we definitely need:
>>>
>>> kvm_interrupts_are_async()
>>>
On 07/23/2012 05:48 PM, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Monday, July 23, 2012 9:12 PM
To: Bhushan Bharat-R65777
Cc: kvm-...@vger.kernel.org; ag...@suse.de; kvm@vger.kernel.org; Bhushan Bharat-
R65777
Subject: Re: [PATCH v2] booke: Added ONE_
On 23 July 2012 17:55, Jan Kiszka wrote:
> On 2012-07-23 17:19, Peter Maydell wrote:
>> OK, let's see if we can get some agreement about naming here.
>>
>> First, some test-functions I think we definitely need:
>>
>> kvm_interrupts_are_async()
>>-- true if interrupt delivery is asynchronous
>
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 user to use, if
> the user lets the work get freed by another threa
On 2012-07-23 17:19, 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 th
Il 23/07/2012 18:44, Blue Swirl ha scritto:
>> > Support for START/STOP UNIT right now is limited to CD-ROMs. This is
>> > wrong,
>> > since removable hard disks (in the real world: SD card readers) also
>> > support
>> > it in pretty much the same way.
> I remember vaguely tuning a set of large
On Mon, Jul 16, 2012 at 2:25 PM, Paolo Bonzini wrote:
> Support for START/STOP UNIT right now is limited to CD-ROMs. This is wrong,
> since removable hard disks (in the real world: SD card readers) also support
> it in pretty much the same way.
I remember vaguely tuning a set of large SCSI hard
Il 03/07/2012 15:20, Paolo Bonzini ha scritto:
> These patches let virtio-blk use the new support for toggling the cache
> mode between writethrough and writeback.
>
> The first patch introduces a new feature bit and configuration field to
> do this. The second patch disables writeback caching fo
On 07/23/2012 11:04 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 9:31 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
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 23, 2012 9:31 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 07/23/2012 10:48 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 9:12 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; ag...@suse.de; kvm@vger.kernel.org; Bhushan
>> Bharat-
>> R65777
>> Subject: Re: [
On 07/23/2012 10:43 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 9:02 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
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 23, 2012 9:12 PM
> To: Bhushan Bharat-R65777
> Cc: kvm-...@vger.kernel.org; ag...@suse.de; kvm@vger.kernel.org; Bhushan
> Bharat-
> R65777
> Subject: Re: [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug
> regi
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 23, 2012 9:02 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/22/2012
On 07/23/2012 06:19 AM, Bharat Bhushan wrote:
> 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
> ---
> v2:
> - Using copy_to/from_user() apis.
>
> arch/powerpc/include/asm/kvm.h | 12 ++
>
On 07/21/2012 03:37 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Saturday, July 21, 2012 2:59 AM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; ag...@suse.de; Bhushan
>> Bharat-
>> R65777
>> Subject: Re:
On 07/22/2012 11:10 PM, Bhushan Bharat-R65777 wrote:
>>> @@ -386,13 +387,23 @@ int kvm_arch_vcpu_init(struct kvm_vcpu *vcpu)
>>> #ifdef CONFIG_KVM_EXIT_TIMING
>>> mutex_init(&vcpu->arch.exit_timing_lock);
>>> #endif
>>> -
>>> +#ifdef CONFIG_BOOKE
>>> + spin_lock_init(&vcpu->arch.wdt_lock);
>
Provide a new function, insn_to_mnemonic, by which e.g. kvm can obtain
a human-readable decoding of an instruction's opcode.
Reviewed-by: Christian Borntraeger
Reviewed-by: Heiko Carstens
Signed-off-by: Cornelia Huck
---
arch/s390/include/asm/processor.h | 1 +
arch/s390/kernel/dis.c
Introduce a new trace system, kvm-s390, for some kvm/s390 specific
trace points:
- injection of interrupts
- delivery of interrupts to the guest
- creation/destruction of kvm machines and vcpus
- stop actions for vcpus
- reset requests for userspace
Reviewed-by: Christian Borntraeger
Signed-off-
Add trace events for several s390 architecture specifics:
- SIE entry/exit
- common intercepts
- common instructions (sigp/diagnose)
Reviewed-by: Christian Borntraeger
Signed-off-by: Cornelia Huck
---
arch/s390/kvm/diag.c | 2 +
arch/s390/kvm/intercept.c | 8 ++
arch/s390/kvm/kvm-s390
Avi, Marcelo,
here's a patch set that introduces trace events for kvm/s390.
It's split into two parts:
- Trace points for architecture-defined events, like intercepts.
This patch calls into the disassembler via the interface provided
by the first patch. These trace points show up under event
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 the check as a proxy for something else, and it sh
On Sun, Jul 22, 2012 at 02:44:23PM -0700, Nicholas A. Bellinger wrote:
> So Linus has merged target-pending/for-next this afternoon, so now we
> are just waiting on net-next to hit mainline with the vhost patches
> already ACK'ed by MST. Hopefully that makes things easier for you to
> considering
On Mon, 23 Jul 2012 17:27:47 +0300
Avi Kivity wrote:
> On 07/23/2012 04:55 PM, Cornelia Huck wrote:
> >> > Basically, we have some flags in our control block we can set so that
> >> > the cpu drops out of SIE whenever external/I/O/... interrupts are
> >> > enabled and then have the host do the lo
On 07/23/2012 04:50 PM, Peter Maydell wrote:
>>
>> Yet.
>
> There is no mechanism in the virtualization extensions to either
> trap on or present a false value for guest accesses to the CPSR
> mode bits. So you can't make the guest OS think it is in Hypervisor
> mode. Therefore you can't provide t
On 07/23/2012 04:55 PM, Cornelia Huck wrote:
>> > Basically, we have some flags in our control block we can set so that
>> > the cpu drops out of SIE whenever external/I/O/... interrupts are
>> > enabled and then have the host do the lowcore updates, psw swaps, etc.
>>
>> Can you write them from a
Currently, kvm allocate some pages and use them as error indicators,
it wastes memory and is not good for scalability. So we use the error
code instead of the pages to indicate the error
Signed-off-by: Xiao Guangrong
---
include/linux/kvm_host.h |3 +-
virt/kvm/async_pf.c |3 +-
vir
In kvm_async_pf_wakeup_all, it uses bad_page to generate broadcast wakeup,
and use put_page to release the page, the work depends on bad_page is the
normal page. But we will use the error code instead of bad_page, so use
kvm_release_page_clean to release the page which will release the error
code p
The current code depends on fault_page is the normal page, but we will
use the error code instead of dummy page in the later patch, so using
kvm_release_pfn_clean to release pfn which will release error code probably
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |2 +-
1 files changed
Currently, kvm allocates some pages and use then as error indicators,
it wastes memory and is not good for scalability.
In this patchset, we introduce some error code instead of the pages to
indicate the error conditions.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the bo
On Mon, 23 Jul 2012 16:14:02 +0300
Avi Kivity wrote:
> On 07/23/2012 04:06 PM, Cornelia Huck wrote:
> > On Mon, 23 Jul 2012 15:18:49 +0300
> > Avi Kivity wrote:
> >
> >> > So, for example, if a specific subchannel (=device) has pending status
> >> > and an I/O interrupt is to be generated, this
On 23 July 2012 14:38, Avi Kivity wrote:
> On 07/23/2012 04:27 PM, Peter Maydell wrote:
>> That seems reasonable, although we have an awkward ordering issue
>> in KVM as it stands: KVM_CREATE_IRQCHIP needs to be called before
>> we start creating VCPU threads (at the moment it is done via kvm_init
On 07/23/2012 04:27 PM, Peter Maydell wrote:
> On 23 July 2012 14:09, Avi Kivity wrote:
>> On 07/23/2012 03:58 PM, Peter Maydell wrote:
>>> So should we be using something other than KVM_CREATE_IRQCHIP to
>>> ask the kernel to create a GIC model for us (and leave KVM_CREATE_IRQCHIP
>>> as a dummy
On 23 July 2012 14:09, Avi Kivity wrote:
> On 07/23/2012 03:58 PM, Peter Maydell wrote:
>> So should we be using something other than KVM_CREATE_IRQCHIP to
>> ask the kernel to create a GIC model for us (and leave KVM_CREATE_IRQCHIP
>> as a dummy "always succeed" ioctl)?
>
> Some time ago I sugges
On 07/23/2012 04:06 PM, Cornelia Huck wrote:
> On Mon, 23 Jul 2012 15:18:49 +0300
> Avi Kivity wrote:
>
>> > So, for example, if a specific subchannel (=device) has pending status
>> > and an I/O interrupt is to be generated, this interrupt remains pending
>> > until an arbitrary cpu is enabled f
On 07/23/2012 03:58 PM, Peter Maydell wrote:
> On 23 July 2012 13:26, Avi Kivity wrote:
>> Really, "irqchip in kernel" means asynchronous interrupts - you can
>> inject an interrupt from outside the vcpu thread. Obviously if the vcpu
>> is sleeping you need to wake it up and that pulls in idle ma
On Mon, 23 Jul 2012 15:18:49 +0300
Avi Kivity wrote:
> > So, for example, if a specific subchannel (=device) has pending status
> > and an I/O interrupt is to be generated, this interrupt remains pending
> > until an arbitrary cpu is enabled for I/O interrupts. If several cpus
> > are enabled for
On 23 July 2012 13:26, Avi Kivity wrote:
> Really, "irqchip in kernel" means asynchronous interrupts - you can
> inject an interrupt from outside the vcpu thread. Obviously if the vcpu
> is sleeping you need to wake it up and that pulls in idle management.
>
> "irqchip" for x86 really means the l
On 07/23/2012 03:31 PM, Avi Kivity wrote:
> On 07/23/2012 03:25 PM, Peter Maydell wrote:
>> On 23 July 2012 13:18, Avi Kivity wrote:
>>> While you don't have an irqchip, you do have asynchronous interrupt
>>> injection, yes? That's what irqchip really is all about.
>>
>> This seems an odd point
On 07/23/2012 03:25 PM, Peter Maydell wrote:
> On 23 July 2012 13:18, Avi Kivity wrote:
>> While you don't have an irqchip, you do have asynchronous interrupt
>> injection, yes? That's what irqchip really is all about.
>
> This seems an odd point of view -- async interrupt injection
> doesn't h
On 07/21/2012 11:54 AM, Peter Maydell wrote:
> On 21 July 2012 07:57, Jan Kiszka wrote:
>> On 2012-07-20 21:14, Peter Maydell wrote:
>>> I'm sure this isn't the only x86ism in the KVM generic source
>>> files. However the thing I'm specifically trying to do is
>>> nuke all the uses of kvm_irqchip_
On 23 July 2012 13:18, Avi Kivity wrote:
> While you don't have an irqchip, you do have asynchronous interrupt
> injection, yes? That's what irqchip really is all about.
This seems an odd point of view -- async interrupt injection
doesn't have anything to do with whether we're modelling
the irq
On 07/23/2012 03:04 PM, Cornelia Huck wrote:
>
> OK, so I was reading through this thread since I want to add irqfd
> support for s390, but we don't have any kind of "irqchip".
>
> The understanding I got so far is that !s390 architectures have some
> kind of mechanism that allows them to "route"
Hi
Please send in any agenda items you are interested in covering.
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
On Sat, 21 Jul 2012 15:16:56 +0200
Jan Kiszka wrote:
> On 2012-07-21 14:57, Peter Maydell wrote:
> > On 21 July 2012 13:35, Jan Kiszka wrote:
> >> On 2012-07-21 14:17, Peter Maydell wrote:
> >>> You still haven't really explained why we can't just ignore irqfd
> >>> for now. I don't see how it w
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
---
v2:
- Using copy_to/from_user() apis.
arch/powerpc/include/asm/kvm.h | 12 ++
arch/powerpc/include/asm/kvm_host.h | 28 ++-
arch/p
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
---
arch/powerpc/include/asm/kvm.h | 12 ++
arch/powerpc/include/asm/kvm_host.h | 28 ++-
arch/powerpc/kvm/booke.c| 64 +++
On 07/18/2012 04:37 PM, Raghavendra K T wrote:
> Currently Pause Loop Exit (PLE) handler is doing directed yield to a
> random vcpu on pl-exit. We already have filtering while choosing
> the candidate to yield_to. This change adds more checks while choosing
> a candidate to yield_to.
>
> On a larg
On 07/23/2012 07:54 AM, Jason Wang wrote:
> On 07/21/2012 08:02 PM, Sasha Levin wrote:
>> On 07/20/2012 03:40 PM, Michael S. Tsirkin wrote:
-err = init_vqs(vi);
> +if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ))
> +vi->has_cvq = true;
> +
>>> How about we disabl
Linus, please pull from the repo and tag at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/kvm-3.6-1
to merge the KVM updates for the 3.5 merge window.
Highlights include
- full big real mode emulation on pre-Westmere Intel hosts (can be disabled
with emulate_invalid_guest_state=0)
-
On 22/07/12 14:43, Avi Kivity wrote:
> On 07/22/2012 03:34 PM, Raghavendra K T wrote:
>>
>> Thanks Marcelo for the review. Avi, Rik, Christian, please let me know
>> if this series looks good now.
>>
>
> It looks fine to me. Christian, is this okay for s390?
>
Tested-by: Christian Borntraeger #
66 matches
Mail list logo
