Hi Jan,
The ubuntu code puts some barrier around the read.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc
You simply override this with your own code - without barrier. Do you think
this is correct?
- Dietmar
--
To unsubscribe
Avi Kivity wrote:
On 11/16/2009 11:22 PM, Jan Kiszka wrote:
Avi Kivity wrote:
On 11/16/2009 07:00 PM, Jan Kiszka wrote:
This patch aims at addressing the mp_state writeback issue in a cleaner
fashion.
What's the issue? the fact that mp_state is updated whenever state is
On 11/17/2009 10:14 AM, Jan Kiszka wrote:
state that is updated outside the vcpu thread. These are particularly
bad since we can't exclude them from updates without excluding other
state as well.
We easily can, using the very same mechanism: No need to overwrite any
of the
Avi Kivity wrote:
On 11/17/2009 10:14 AM, Jan Kiszka wrote:
state that is updated outside the vcpu thread. These are particularly
bad since we can't exclude them from updates without excluding other
state as well.
We easily can, using the very same mechanism: No need to overwrite
Jan Kiszka wrote:
Dietmar Maurer wrote:
Hi Jan,
The ubuntu code puts some barrier around the read.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc
You simply override this with your own code - without barrier. Do you think
The ubuntu code puts some barrier around the read.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc
You simply override this with your own code - without barrier. Do you
think this is correct?
Unless I messed it up
Hi,
Has anyone noticed that since Fedora Kernel 2.6.27.30-170.2.82.fc10.i686.PAE
smb doesn't work anymore? My guest system (Windows XP SP3) crashes on
accessing the smb share. My hope was this bug would be fixed after
upgrading to Fedora 11, but unfortunately is isn't.
Regards,
Luuk
--
To
On Monday 16 November 2009 11:12:19 Avi Kivity wrote:
Anyways, I'm just curious, as this feature is
primarily interesting for development, IMHO.
No, it's primarily interesting for performance.
I think I confused NPT with support for nested virtualization (which I think
no one except devs
Avi Kivity wrote:
On 11/16/2009 04:18 PM, Fernando Luis Vázquez Cao wrote:
Avi Kivity wrote:
On 11/09/2009 05:53 AM, Fernando Luis Vázquez Cao wrote:
Kemari runs paired virtual machines in an active-passive configuration
and achieves whole-system replication by continuously copying the
state
On 11/17/2009 11:59 AM, Jan Kiszka wrote:
Jan Kiszka wrote:
Dietmar Maurer wrote:
Hi Jan,
The ubuntu code puts some barrier around the read.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc
You simply override this with
On 11/17/2009 11:16 AM, Jan Kiszka wrote:
That's because qemu has no need for this. But kvm is more than just
serving qemu, we try to be more general. That said, I can't really see
anyone wanting to arbitrarily inject an exception.
Well, the current API comes with millions of ways to
Avi Kivity wrote:
On 11/17/2009 11:16 AM, Jan Kiszka wrote:
That's because qemu has no need for this. But kvm is more than just
serving qemu, we try to be more general. That said, I can't really see
anyone wanting to arbitrarily inject an exception.
Well, the current API comes with
qemu-kvm's switch to seabios uncovered a regression with cdrom
handling. Vista x64 no longer recognizes the cdrom, while pc-bios still
works. Installing works, but that uses int 13, not the native driver.
Haven't investigated further yet.
Command line:
qemu -drive
On 11/17/2009 03:05 PM, Jan Kiszka wrote:
Problem is, the inject channels are implied (APIC messages in smp
guests). Documentation is good, but if we can avoid it that's better.
Note the only way to rmw vcpu events during smp is pausing the guest,
because of this race.
That's what
2009/11/17 Avi Kivity a...@redhat.com:
On 11/17/2009 01:04 PM, Yoshiaki Tamura wrote:
What I mean is:
- choose synchronization point A
- start copying memory for synchronization point A
- output is delayed
- choose synchronization point B
- copy memory for A and B
if guest touches
Avi Kivity wrote:
On 11/17/2009 03:05 PM, Jan Kiszka wrote:
Problem is, the inject channels are implied (APIC messages in smp
guests). Documentation is good, but if we can avoid it that's better.
Note the only way to rmw vcpu events during smp is pausing the guest,
because of this race.
On 11/17/2009 04:12 PM, Jan Kiszka wrote:
The alternative would be a complex getlock/putunlock + a queue for
async events during the lock + an option to ignore what was queued when
doing a true reset. Back to square #1: we would still need the proposed
high-level interface to communicate the
Hi,
We find a little mistake with ending of allocator.py.
Because I send this patch today. I resend whole repaired patch again.
- Original Message -
From: Jiri Zupka jzu...@redhat.com
To: autotest autot...@test.kernel.org, kvm kvm@vger.kernel.org
Cc: u...@redhat.com
Sent: Tuesday,
Bugs item #2896992, was opened at 2009-11-13 05:58
Message generated for change (Comment added) made by
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2896992group_id=180599
Please note that this message will contain a full copy of the comment thread,
Avi Kivity wrote:
On 11/17/2009 04:12 PM, Jan Kiszka wrote:
The alternative would be a complex getlock/putunlock + a queue for
async events during the lock + an option to ignore what was queued when
doing a true reset. Back to square #1: we would still need the proposed
high-level interface
Jan Kiszka wrote:
Avi Kivity wrote:
On 11/17/2009 04:12 PM, Jan Kiszka wrote:
The alternative would be a complex getlock/putunlock + a queue for
async events during the lock + an option to ignore what was queued when
doing a true reset. Back to square #1: we would still need the proposed
On 11/17/2009 06:50 PM, Jan Kiszka wrote:
I think we're not on the same page here. As I see it, no interface
change is needed at all.
It's true that existing kernels don't handle this properly, which is why
I said I'm willing to treat it as a bug (and thus the -stable treatment
etc.). I
Avi Kivity wrote:
On 11/17/2009 11:59 AM, Jan Kiszka wrote:
Jan Kiszka wrote:
Dietmar Maurer wrote:
Hi Jan,
The ubuntu code puts some barrier around the read.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc
You
Avi Kivity schrieb:
qemu-kvm's switch to seabios uncovered a regression with cdrom
handling. Vista x64 no longer recognizes the cdrom, while pc-bios
still works. Installing works, but that uses int 13, not the native
driver. Haven't investigated further yet.
Command line:
qemu -drive
server/autotest.py was referencing it but it didn't exist.
This patch creates the error class.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/common_lib/error.py |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/client/common_lib/error.py
Right now autotest will drop caches between:
* Test executions
* Same test iterations
This change turns those into configurable options on
global_config.ini. The default values were added on the
previous patch.
2nd attempt: Now global config support for stand alone client
runs was
In order to make it possible the autotest client to use the
global_config.ini configuration files:
* Modified global_config.py to support verifying if the
configuration file is under autotest's root directory,
or the client directory
* Extended the autotest run method to copy over
the
Jim Paris wrote:
Erik Rull wrote:
Hi all,
I want to run an epson inkjet within my windows xp guest. my host has
enabled usb 2.0, the USB flashdrive works without any problems. When I
plug in the printer (works with the same drivers on a native windows
xp!), it is recognized and the status
Rodrigo Campos wrote:
On Tue, Nov 17, 2009 at 12:01:08AM +0100, Erik Rull wrote:
Erik Rull wrote:
Any Ideas? I also tested other IRQ lines and other ttyS* on the
system - same behaviour.
fixed, apic on host side was disabled, kvm / qemu seems to need it.
I think I hit the same issue. What
On Tue, Nov 17, 2009 at 9:40 AM, Lucas Meneghel Rodrigues
l...@redhat.com wrote:
In order to make it possible the autotest client to use the
global_config.ini configuration files:
* Modified global_config.py to support verifying if the
configuration file is under autotest's root directory,
On Tue, Nov 17, 2009 at 07:00:56PM +0100, Erik Rull wrote:
Rodrigo Campos wrote:
On Tue, Nov 17, 2009 at 12:01:08AM +0100, Erik Rull wrote:
Erik Rull wrote:
Any Ideas? I also tested other IRQ lines and other ttyS* on the
system - same behaviour.
fixed, apic on host side was disabled, kvm /
Saul Tamari wrote:
This patch reduces the size of memory being cleared on every virtio-blk IO.
Improve number of IOPS when using avirtio-blk device.
On every virtio-blk IO command passed to QEMU, virtio_blk_alloc_request()
allocates and clears (with qemu_mallocz()) a VirtIOBlockReq object.
The
To really check for sure that we're not using any pv-ops code by accident,
we should make sure that we don't even export the structures used to access
pv-ops exported functions.
So let's surround the pv-ops structs by #ifdefs.
Signed-off-by: Alexander Graf ag...@suse.de
---
Currently when using paravirt ops it's an all-or-nothing option. We can either
use pv-ops for CPU, MMU, timing, etc. or not at all.
Now there are some use cases where we don't need the full feature set, but only
a small chunk of it. KVM is a pretty prominent example for this.
So let's make
Currently selecting KVM guest support enabled multiple features at once that
not everyone necessarily wants to have, namely:
- PV MMU
- zero io delay
- apic detection workaround
Let's split them off so we don't drag in the full pv-ops framework just to
detect we're running on KVM. That gives
Paravirt ops is currently only capable of either replacing a lot of Linux
internal code or none at all. The are users that don't need all of the
possibilities pv-ops delivers though.
On KVM for example we're perfectly fine not using the PV MMU, thus not
touching any MMU code. That way we don't
Right now autotest will drop caches between:
* Test executions
* Same test iterations
This change turns those into configurable options on
global_config.ini. The default values were added on the
previous patch.
2nd attempt: Now global config support for stand alone client
runs was
In order to make it possible the autotest client to use the
global_config.ini configuration files:
* Modified global_config.py to support verifying if the
configuration file is under autotest's root directory,
or the client directory
* Extended the autotest run method to copy over
the
On Wed, 18 Nov 2009 10:43:12 am Alexander Graf wrote:
Currently selecting KVM guest support enabled multiple features at once that
not everyone necessarily wants to have, namely:
These patches make perfect sense, but please make sure Jeremy Fitzhardinge
(CC'd) is in the loop, as he split the
On 18.11.2009, at 02:33, Rusty Russell wrote:
On Wed, 18 Nov 2009 10:43:12 am Alexander Graf wrote:
Currently selecting KVM guest support enabled multiple features at
once that
not everyone necessarily wants to have, namely:
These patches make perfect sense, but please make sure Jeremy
In order to make it possible the autotest client to use the
global_config.ini configuration files:
* Modified global_config.py to support verifying if the
configuration file is under autotest's root directory,
or the client directory
* Extended the autotest run method to copy over
the
server/autotest.py was referencing it but it didn't exist.
This patch creates the error class.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/common_lib/error.py |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/client/common_lib/error.py
server/autotest.py was referencing it but it didn't exist.
This patch creates the error class.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/common_lib/error.py |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/client/common_lib/error.py
Bugs item #2896992, was opened at 2009-11-13 05:58
Message generated for change (Comment added) made by
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2896992group_id=180599
Please note that this message will contain a full copy of the comment thread,
On Tue, Nov 17, 2009 at 03:21:31PM +0200, Avi Kivity wrote:
qemu-kvm's switch to seabios uncovered a regression with cdrom handling.
Vista x64 no longer recognizes the cdrom, while pc-bios still works.
Installing works, but that uses int 13, not the native driver. Haven't
investigated
Right. So the kvm-kmod replacement is also fine.
Dietmar, if you could confirm that your issue is fixed,
Yes, it is fixed.
--
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
46 matches
Mail list logo
