Il 08/02/2013 05:05, Rusty Russell ha scritto:
> Paolo Bonzini writes:
>> The virtqueue_add_buf function has two limitations:
>>
>> 1) it requires the caller to provide all the buffers in a single call;
>>
>> 2) it does not support chained scatterlists: the buffers must be
>> provided as an array
Paolo Bonzini writes:
> The virtqueue_add_buf function has two limitations:
>
> 1) it requires the caller to provide all the buffers in a single call;
>
> 2) it does not support chained scatterlists: the buffers must be
> provided as an array of struct scatterlist.
>
> Because of these limitations
On Thu, Feb 07, 2013 at 03:52:24PM +0200, Gleb Natapov wrote:
> > Its not a bad idea to have a new KVM_REQ_ bit for PIR processing (just
> > as the current patches do).
> Without the numbers I do not see why.
KVM_REQ_EVENT already means... counting... many things. Its a well
defined request, to sy
On Wed, Jan 23, 2013 at 03:19:22PM +0800, Hu Tao wrote:
> This patch enables preservation of cpu runstate during save/load vm.
> So when a vm is restored from snapshot, the cpu runstate is restored,
> too.
>
> See following example:
>
> # save two vms: one is running, the other is paused
> (qemu)
On Wed, Jan 23, 2013 at 03:19:23PM +0800, Hu Tao wrote:
> From: Wen Congyang
>
> The guest should run after resetting it, but it does not run if its
> old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
>
> We don't set runstate to RUN_STATE_PAUSED when resetting the guest,
> so the runst
Hi,
On Wed, Jan 23, 2013 at 03:19:21PM +0800, Hu Tao wrote:
> We can know the guest is panicked when the guest runs on xen.
> But we do not have such feature on kvm.
>
> Another purpose of this feature is: management app(for example:
> libvirt) can do auto dump when the guest is panicked. If mana
On 08.02.2013, at 01:22, Scott Wood wrote:
> On 02/07/2013 06:20:33 PM, Alexander Graf wrote:
>> On 07.02.2013, at 23:17, Scott Wood wrote:
>> > Commit 2765788fcc3dc64920dd2be3d32319b50b1e2813 ("KVM: PPC: BookE: Handle
>> > alignment interrupts") broke the build by adding mismatched parentheses.
On 02/07/2013 06:20:33 PM, Alexander Graf wrote:
On 07.02.2013, at 23:17, Scott Wood wrote:
> Commit 2765788fcc3dc64920dd2be3d32319b50b1e2813 ("KVM: PPC: BookE:
Handle
> alignment interrupts") broke the build by adding mismatched
parentheses.
>
> Signed-off-by: Scott Wood
Thanks a lot fo
On 07.02.2013, at 23:17, Scott Wood wrote:
> Commit 2765788fcc3dc64920dd2be3d32319b50b1e2813 ("KVM: PPC: BookE: Handle
> alignment interrupts") broke the build by adding mismatched parentheses.
>
> Signed-off-by: Scott Wood
Thanks a lot for catching this.
This patch hasn't gone into kvm-ppc-n
Am Thu, 07 Feb 2013 15:49:58 -0700
schrieb Alex Williamson :
> > If I whitelist pcieport USB3 works within the guests. :-)
> > Binding 1c.0 and 1c.6 is no longer needed.
> > Next week I'll run some more tests with USB3 devices.
>
> Great! Thanks for the test. I assume you didn't need to do anyth
On Thu, 2013-02-07 at 23:23 +0100, Richard Weinberger wrote:
> Hi,
>
> Am Wed, 06 Feb 2013 15:45:37 -0700
> schrieb Alex Williamson :
>
> > On Wed, 2013-02-06 at 21:25 +0100, Richard Weinberger wrote:
> > > Hi,
> > >
> > > Am Wed, 06 Feb 2013 11:47:20 -0700
> > > schrieb Alex Williamson :
> > >
Hi,
Am Wed, 06 Feb 2013 15:45:37 -0700
schrieb Alex Williamson :
> On Wed, 2013-02-06 at 21:25 +0100, Richard Weinberger wrote:
> > Hi,
> >
> > Am Wed, 06 Feb 2013 11:47:20 -0700
> > schrieb Alex Williamson :
> > > Does the card work with pci-assign or are both broken?
> >
> > It works with pc
Commit 2765788fcc3dc64920dd2be3d32319b50b1e2813 ("KVM: PPC: BookE: Handle
alignment interrupts") broke the build by adding mismatched parentheses.
Signed-off-by: Scott Wood
---
Against kvm-ppc-queue
arch/powerpc/kvm/booke_interrupts.S |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On Thu, Feb 07, 2013 at 04:01:11PM +0200, Gleb Natapov wrote:
> On Wed, Feb 06, 2013 at 08:49:23PM -0200, Marcelo Tosatti wrote:
> > > Second is that interrupt may be
> > > reported as delivered, but it will be coalesced (possible only with the
> > > self
> > > IPI with the same vector):
> > >
>
On Thu, Feb 07, 2013 at 04:41:31PM +0100, Erik Brakkee wrote:
> Hi,
>
>
> We have been benchmarking a java server application (java 6 update 29)
> that requires a mysql database. The scenario is quite simple. We open a
> web page which displays a lot of search results. To get the content of the
>
From: David Daney
Uniform definitions for both 32-bit and 64-bit MIPS machines.
Signed-off-by: David Daney
Cc: Sanjay Lal
Cc: kvm@vger.kernel.org
---
Previously Sanjay posted a version of asm/kvm.h that worked only for
32-bit MIPS machines. Since the MIPS kernel port also supports 64-bit
CPU
Guys,
I've once more updated the branches for KVM/arm64
- kvm-arm/pre-arm64: KVM/ARM stable branches + the "cleanup" branch +
some basic perf support
- kvm-arm/vgic-fixes: as the name says, a couple of pending VGIC related
fixes.
- arm64/soc-armv8-model: Catalin Marinas' arm64 branch
- kvm-arm
Hi,
We have been benchmarking a java server application (java 6 update 29)
that requires a mysql database. The scenario is quite simple. We open a
web page which displays a lot of search results. To get the content of the
page one big query is done with many smaller queries to retrieve the data.
On 07.02.2013, at 16:25, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-ow...@vger.kernel.org] On
>> Behalf Of Alexander Graf
>> Sent: Thursday, February 07, 2013 8:29 PM
>> To: Wood Scott-B07421
>> Cc: Bhushan Bharat-R65777
On Thu, Feb 7, 2013 at 4:19 PM, Stefan Hajnoczi wrote:
CCed libvir-list to see if libvirt would like to do a joint
application with QEMU.
As mentioned, it's early days and GSoC 2013 has not been announced
yet. I just want to start gathering ideas and seeing who is willing
to mentor this year.
S
> -Original Message-
> From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-ow...@vger.kernel.org] On
> Behalf Of Alexander Graf
> Sent: Thursday, February 07, 2013 8:29 PM
> To: Wood Scott-B07421
> Cc: Bhushan Bharat-R65777; kvm-...@vger.kernel.org; kvm@vger.kernel.org
> Subject: Re: [PAT
On 07.02.2013, at 16:00, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Saturday, February 02, 2013 4:09 AM
>> To: Alexander Graf
>> Cc: Bhushan Bharat-R65777; kvm-...@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 8/8] KVM:PPC:bo
On 07.02.2013, at 15:48, Bhushan Bharat-R65777 wrote:
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, January 25, 2013 5:13 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; Bh
> -Original Message-
> From: Wood Scott-B07421
> Sent: Saturday, February 02, 2013 4:09 AM
> To: Alexander Graf
> Cc: Bhushan Bharat-R65777; kvm-...@vger.kernel.org; kvm@vger.kernel.org
> Subject: Re: [PATCH 8/8] KVM:PPC:booke: Allow debug interrupt injection to
> guest
>
> On 01/31/201
On 01.02.2013, at 23:38, Scott Wood wrote:
> On 01/31/2013 06:11:32 PM, Alexander Graf wrote:
>> On 31.01.2013, at 23:40, Scott Wood wrote:
>> > On 01/31/2013 01:20:39 PM, Alexander Graf wrote:
>> >> On 31.01.2013, at 20:05, Alexander Graf wrote:
>> >> >
>> >> > On 31.01.2013, at 19:54, Scott Woo
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, January 25, 2013 5:13 PM
> To: Bhushan Bharat-R65777
> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; Bhushan
> Bharat-R65777
> Subject: Re: [
On 04.02.2013, at 07:12, Bhushan Bharat-R65777 wrote:
> Hi Alex/Scott,
>
> Below is my understanding about the ONE_REG interface requirement for timer
> registers.
>
> Define the below 2 ONE_REG interface for TSR access:
> KVM_REG_SET_TSR, // Set the specified bits in TSR
s/SET/OR/
>
On 04.02.2013, at 01:41, Paul Mackerras wrote:
> On Wed, Jan 16, 2013 at 01:54:41PM +0530, Bharat Bhushan wrote:
>> This patch adds the one_reg interface to get the special instruction
>> to be used for setting software breakpoint from userspace.
>
> Since this presumably is constant for any giv
On 02/07/2013 02:46 AM, Glauber Costa wrote:
On 02/06/2013 10:07 PM, Michael Wolf wrote:
On 02/06/2013 08:36 AM, Glauber Costa wrote:
On 02/06/2013 01:49 AM, Michael Wolf wrote:
Add a helper routine to scheduler/core.c to allow the kvm module
to retrieve the cpu hardlimit settings. The values
On 02/06/2013 03:18 PM, Rik van Riel wrote:
On 02/05/2013 04:49 PM, Michael Wolf wrote:
Change the paravirt calls that retrieve the steal-time information
from the host. Add to it getting the consigned value as well as
the steal time.
Signed-off-by: Michael Wolf
diff --git a/arch/x86/includ
On 02/06/2013 03:14 PM, Rik van Riel wrote:
On 02/05/2013 04:49 PM, Michael Wolf wrote:
Expand the steal time msr to also contain the consigned time.
Signed-off-by: Michael Wolf
---
arch/x86/include/asm/paravirt.h |4 ++--
arch/x86/include/asm/paravirt_types.h |2 +-
arch/x86
On 01.02.2013, at 10:09, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, February 01, 2013 1:34 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 0/8] KVM: BOO
On 01.02.2013, at 10:07, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, February 01, 2013 1:36 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 3/8] KVM: PPC
On Wed, Feb 06, 2013 at 08:49:23PM -0200, Marcelo Tosatti wrote:
> > Second is that interrupt may be
> > reported as delivered, but it will be coalesced (possible only with the self
> > IPI with the same vector):
> >
> > Starting condition: PIR=0, IRR=0 vcpu is in a guest mode
> >
> > io thread
On Wed, Feb 06, 2013 at 10:24:06PM -0200, Marcelo Tosatti wrote:
> On Wed, Feb 06, 2013 at 08:49:23PM -0200, Marcelo Tosatti wrote:
> > On Tue, Feb 05, 2013 at 09:32:50AM +0200, Gleb Natapov wrote:
> > > On Mon, Feb 04, 2013 at 06:47:30PM -0200, Marcelo Tosatti wrote:
> > > > On Mon, Feb 04, 2013 a
Il 07/02/2013 14:31, Michael S. Tsirkin ha scritto:
> > Single means *this piece* (for example a request header) is single. It
> > could still end up in an indirect buffer because QEMU does not support
> > mixed direct/indirect buffers.
>
> Yes but why is the optimization worth it?
> It makes sen
On Thu, Feb 07, 2013 at 02:20:53PM +0100, Paolo Bonzini wrote:
> Il 07/02/2013 14:23, Michael S. Tsirkin ha scritto:
> > On Thu, Feb 07, 2013 at 02:14:24PM +0100, Paolo Bonzini wrote:
> >> Il 07/02/2013 14:09, Michael S. Tsirkin ha scritto:
> One major difference between virtqueue_add_buf and
Il 07/02/2013 14:23, Michael S. Tsirkin ha scritto:
> On Thu, Feb 07, 2013 at 02:14:24PM +0100, Paolo Bonzini wrote:
>> Il 07/02/2013 14:09, Michael S. Tsirkin ha scritto:
One major difference between virtqueue_add_buf and virtqueue_add_sg
is that the latter uses scatterlist iterators, wh
On Thu, Feb 07, 2013 at 02:14:24PM +0100, Paolo Bonzini wrote:
> Il 07/02/2013 14:09, Michael S. Tsirkin ha scritto:
> >> One major difference between virtqueue_add_buf and virtqueue_add_sg
> >> is that the latter uses scatterlist iterators, which follow chained
> >> scatterlist structs and stop at
Il 07/02/2013 14:09, Michael S. Tsirkin ha scritto:
>> One major difference between virtqueue_add_buf and virtqueue_add_sg
>> is that the latter uses scatterlist iterators, which follow chained
>> scatterlist structs and stop at ending markers. In order to avoid code
>> duplication, and use the ne
On Thu, Feb 07, 2013 at 01:22:24PM +0100, Paolo Bonzini wrote:
> The virtqueue_add_buf function has two limitations:
>
> 1) it requires the caller to provide all the buffers in a single call;
>
> 2) it does not support chained scatterlists: the buffers must be
> provided as an array of struct sca
On Thu, Feb 07 2013, Paolo Bonzini wrote:
> This is useful in places that recycle the same scatterlist multiple
> times, and do not want to incur the cost of sg_init_table every
> time in hot paths.
Looks fine to me.
Acked-by: Jens Axboe
--
Jens Axboe
--
To unsubscribe from this list: send th
The virtqueue_add_buf function has two limitations:
1) it requires the caller to provide all the buffers in a single call;
2) it does not support chained scatterlists: the buffers must be
provided as an array of struct scatterlist.
Because of these limitations, virtio-scsi has to copy each reque
Move the creation of the request header and response footer to
__virtblk_add_req. vbr->sg only contains the data scatterlist,
the header/footer are added separately using the new piecewise
API for building virtqueue buffers.
With this change, virtio-blk is not relying anymore on the virtio
functi
Prepare for when virtqueue_add_buf will use sg_next instead of
ignoring ending markers.
Note that for_each_sg (and thus virtqueue_add_buf) allows you
to pass a "truncated" scatterlist that does not have a marker
on the last item. We rely on this in add_recvbuf_mergeable.
Signed-off-by: Paolo Bon
This is similar to the previous patch, but a bit more radical
because the bio and req paths now share the buffer construction
code. Because the req path doesn't use vbr->sg, however, we
need to add a couple of arguments to __virtblk_add_req.
We also need to teach __virtblk_add_req how to build SC
Right now, both virtblk_add_req and virtblk_add_req_wait call
virtqueue_add_buf. To prepare for the next patches, abstract the call
to virtqueue_add_buf into a new function __virtblk_add_req, and include
the waiting logic directly in virtblk_add_req.
Signed-off-by: Paolo Bonzini
---
drivers/blo
The virtqueue_add_buf function has two limitations:
1) it requires the caller to provide all the buffers in a single call;
2) it does not support chained scatterlists: the buffers must be
provided as an array of struct scatterlist.
Because of these limitations, virtio-scsi has to copy each reque
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for the lock).
The speedup is relatively small (2-4%) but it is worthwhile because of
the code simplification it enables. A
Eliminate the code duplication between virtqueue_add_buf and
virtqueue_add_sg. That's safe to do now that no devices will
pass scatterlists with a termination marker in the middle.
Signed-off-by: Paolo Bonzini
---
drivers/virtio/virtio_ring.c | 157 +++---
1
This is useful in places that recycle the same scatterlist multiple
times, and do not want to incur the cost of sg_init_table every
time in hot paths.
Cc: Jens Axboe
Signed-off-by: Paolo Bonzini
---
Jens, could you give your Acked-by for this patch?
block/blk-integrity.c |2 +
There are two ways to express an interruption subclass:
- As a bitmask, as used in cr6.
- As a number, as used in the I/O interruption word.
Unfortunately, we have treated the I/O interruption word as if it
contained the bitmask as well, which went unnoticed so far as
- (not-yet-released) qemu mad
Hi,
here's another kvm-s390 bugfix for kvm-next, this time fixing a
thinko in the I/O interrupt injection.
Please apply.
Cornelia Huck (1):
KVM: s390: Fix handling of iscs.
arch/s390/kvm/interrupt.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
--
1.7.12.4
--
T
This field was needed to differentiate memory slots created by the new
API, KVM_SET_USER_MEMORY_REGION, from those by the old equivalent,
KVM_SET_MEMORY_REGION, whose support was dropped long before:
commit b74a07beed0e64bfba413dcb70dd6749c57f43dc
KVM: Remove kernel-allocated memory regions
A
On 02/06/2013 10:07 PM, Michael Wolf wrote:
> On 02/06/2013 08:36 AM, Glauber Costa wrote:
>> On 02/06/2013 01:49 AM, Michael Wolf wrote:
>>> Add a helper routine to scheduler/core.c to allow the kvm module
>>> to retrieve the cpu hardlimit settings. The values will be used
>>> to set up a timer t
55 matches
Mail list logo
