On 05/30/14 15:45, Paolo Bonzini wrote:
I was thinking of removing it in Linux 3.17. I'm not even sure it
compiles right now, hasn't seen any action in years, and all open-source
userspace code to use it has been dead for years.
If you disagree, please speak up loudly in the next month.
On 02/18/12 14:25, Stefan Hajnoczi wrote:
On Fri, Feb 17, 2012 at 3:31 PM, Pete Ashdown pashd...@xmission.com wrote:
On 02/17/2012 04:30 AM, Stefan Hajnoczi wrote:
On Fri, Feb 17, 2012 at 4:57 AM, Pete Ashdown pashd...@xmission.com
wrote:
I've been waiting for some response from the
On 01/15/12 22:05, Ryar wrote:
Hi
I'd like to install a few servers as kvm guests in my home network and
to keep host as minimal as possible I'm thinking to install xbmc as a
guest too
1. Is is feasible ? As I read xbmc heavily uses opengl and I'm not sure
what about sound
2. Is it
Hi,
For those who are interested, I have posted the notes from the 2011
Linux Plumbers Virtualization micro conference here:
http://wiki.linuxplumbersconf.org/2011:virtualization
Slides can be found by clicking on the presentation and going onto the
Plumbers abstracts.
Cheers,
Jes
--
To
On 07/25/11 12:06, Stefan Hajnoczi wrote:
+#define QEMU_NEW(type) ((type *)(qemu_malloc(sizeof(type
+#define QEMU_NEWZ(type) ((type *)(qemu_mallocz(sizeof(type
Does this mean we need to duplicate the type name for each allocation?
struct foo *f;
...
f = qemu_malloc(sizeof(*f));
On 07/25/11 17:15, Anthony Liguori wrote:
On 07/25/2011 10:10 AM, Jes Sorensen wrote:
On 07/25/11 12:06, Stefan Hajnoczi wrote:
+#define QEMU_NEW(type) ((type *)(qemu_malloc(sizeof(type
+#define QEMU_NEWZ(type) ((type *)(qemu_mallocz(sizeof(type
Does this mean we need to duplicate
On 07/25/11 17:20, Avi Kivity wrote:
On 07/25/2011 06:17 PM, Jes Sorensen wrote:
Using the commands consistently does have an impact, and at least with
qemu_malloc() it is obvious what they are and how they behave. The
proposed macros on the other hand requires everybody to go look up
On 07/25/11 17:24, Avi Kivity wrote:
On 07/25/2011 06:21 PM, Jes Sorensen wrote:
On 07/25/11 17:20, Avi Kivity wrote:
On 07/25/2011 06:17 PM, Jes Sorensen wrote:
Using the commands consistently does have an impact, and at least
with
qemu_malloc() it is obvious what they are and how
On 05/09/11 13:50, Juan Quintela wrote:
Please send in any agenda items you are interested in covering.
From last week, we have already:
- import kvm headers into qemu, drop #ifdef maze (Jan)
Thanks, Juan.
Since we haven't received any further agenda items. In addition Anthony
is
On 05/03/11 07:58, Jagane Sundar wrote:
On 5/2/2011 7:36 AM, Jes Sorensen wrote:
Reading your page, the first thing I stumble upon under 'Use Cases' is
the reference to EBS storage. What is that?
EBS stands for Elastic Block Storage - Amazon EC2's shared storage
solution. This is the storage
On 05/03/11 15:04, Jan Kiszka wrote:
On 2011-05-03 12:21, Juan Quintela wrote:
Please send in any agenda items you are interested in covering.
Provided there will be more topics:
- import kvm headers into qemu, drop #ifdef maze
Otherwise, we can also discuss this based on the patch I'm
On 05/02/11 00:23, Jagane Sundar wrote:
Having a live backup feature for kvm will make it a better solution for
IaaS clouds compared to xen. I would like to solicit feedback from all
of you folks involved in the block subsystem of qemu. Stefan mentioned
that Jes is the person most intimately
On 04/26/11 11:24, Juan Quintela wrote:
Please, send in any agenda items you are interested in covering.
From last week:
Tools for resource accounting the virtual machines.
Luis Antonio Galindo Castro (FunkyM0nk3y) funkymons...@gmail.com
- Status of glib tree - next steps?
Jes
On 04/26/11 15:09, Anthony Liguori wrote:
On 04/26/2011 06:47 AM, Jes Sorensen wrote:
On 04/26/11 11:24, Juan Quintela wrote:
Please, send in any agenda items you are interested in covering.
From last week:
Tools for resource accounting the virtual machines.
Luis Antonio Galindo
On 03/14/11 13:14, Juan Quintela wrote:
Please send any agenda items you are interested in covering.
Thanks, Juan.
I presume you mean for March 15? Today is the 14th and it is Monday :)
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
Hello,
Please find attached my notes from the weekly QEMU/KVM call January 25,
2011. My apologies if I got something wrong.
Jes
- QEMU 0.14/0.15 releases
- Feb 1st 2011 branch to stable tree for 0.14. Anthony would like to
do a formal release quickly, so hopefully within 1-2 weeks after
On 01/10/11 12:59, Juan Quintela wrote:
Juan Quintela quint...@redhat.com wrote:
Now sent it to the right kvm list. Sorry for the second sent.
Please send any agenda items you are interested in covering.
- KVM Forum 2011 (Jes).
Just to add a bit more background. Last year we discussed
On 01/03/11 11:57, Juan Quintela wrote:
Please send any agenda items you are interested in covering.
thanks, Juan.
Do we have anything for the agenda yet?
Jes
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
On 01/04/11 15:33, Anthony Liguori wrote:
On 01/04/2011 08:31 AM, Jes Sorensen wrote:
On 01/03/11 11:57, Juan Quintela wrote:
Please send any agenda items you are interested in covering.
thanks, Juan.
Do we have anything for the agenda yet?
I could use the extra hour
On 12/14/10 01:12, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
thanks,
-chris
Chris,
Any chance you could fix your cronjob to send out the CFA a day earlier?
15 hrs before is a bit short notice.
Cheers,
Jes
--
To unsubscribe from this list: send
On 12/07/10 00:51, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
thanks,
-chris
No agenda, no replies
Call canceled I presume?
Jes
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
files changed, 62 insertions(+), 2 deletions(-)
Hi Hidetoshi,
This looks good to me!
Acked-by: Jes Sorensen jes.soren...@redhat.com
Cheers,
Jes
--
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
On 11/24/10 13:59, Alexander Graf wrote:
On 24.11.2010, at 11:52, Avi Kivity wrote:
Introduce exception-safe objects for calling system, vm, and vcpu ioctls.
Signed-off-by: Avi Kivity a...@redhat.com
FWIW, I still disagree with C++ and believe this code to be hardly readable.
YUCK!
On 11/24/10 16:50, Anthony Liguori wrote:
On 11/24/2010 09:40 AM, Gleb Natapov wrote:
On Wed, Nov 24, 2010 at 08:41:26AM -0600, Anthony Liguori wrote:
In real hardware, the i8042 (keyboard controller) is actually
implemented in the PIIX3 which is a chip that is part of the i440fx.
The i440fx
On 11/24/10 17:34, Avi Kivity wrote:
On 11/24/2010 06:29 PM, Jes Sorensen wrote:
FWIW, I still disagree with C++ and believe this code to be hardly
readable.
YUCK!
It's got :'s all over the place that makes no sense whatsoever :(
You've got two in one sentence! Practice what you
On 11/24/10 17:47, Avi Kivity wrote:
On 11/24/2010 06:40 PM, Jes Sorensen wrote:
Well the problem here is that the i8042 is in the i440fx.c file, it
shouldn't be there in the first place. The gluing together things in
silicon is really just a way to shorten the wires and make it easier
On 11/24/10 17:53, Anthony Liguori wrote:
On 11/24/2010 10:40 AM, Jes Sorensen wrote:
Well the problem is the 10% you are talking about is another 30% loss
because the code is now practically unreadable, plus you open up the can
of worms that people will start using some of the totally
On 11/24/10 17:59, Avi Kivity wrote:
On 11/24/2010 06:51 PM, Jes Sorensen wrote:
Right we need good design for our C code, which we are lacking to a
large extend. However that has nothing to do with the language, that has
to do with the developers.
I'm sure patches will be welcome.
C
On 11/24/10 18:07, Avi Kivity wrote:
On 11/24/2010 07:02 PM, Gleb Natapov wrote:
On Wed, Nov 24, 2010 at 06:56:52PM +0200, Avi Kivity wrote:
On 11/24/2010 06:52 PM, Gleb Natapov wrote:
Plus some magic glue. You can't say it is an ISA bridge. It's
exactly what its spec says it
On 11/24/10 18:11, Avi Kivity wrote:
On 11/24/2010 07:06 PM, Jes Sorensen wrote:
Sorry but that is utterly and completely bogus! The enforcement is only
as good as the developers and maintainers make it,
class File {
public:
virtual ~File() {}
virtual void read(...) = 0
On 11/24/10 18:25, Avi Kivity wrote:
On 11/24/2010 07:17 PM, Jes Sorensen wrote:
In the mean time we spend our time debugging the runtime because the
virtual functions don't behave as expected. In C we know what is going
on, in C++ it is pray and hope.
That is pure bullshit. All major
On 11/24/10 18:27, Anthony Liguori wrote:
The compiler won't generate an error. Only upon a call to
file_release() will a null pointer dereference happens whereas in C++,
because this paradigm is structured in the language, the compiler can
help assist you.
Explicit code means you know what
On 11/24/10 18:41, Avi Kivity wrote:
On 11/24/2010 07:36 PM, Jes Sorensen wrote:
On 11/24/10 18:27, Anthony Liguori wrote:
The compiler won't generate an error. Only upon a call to
file_release() will a null pointer dereference happens whereas in C++,
because this paradigm
On 11/24/10 18:43, Anthony Liguori wrote:
On 11/24/2010 11:36 AM, Jes Sorensen wrote:
On 11/24/10 18:27, Anthony Liguori wrote:
The compiler won't generate an error. Only upon a call to
file_release() will a null pointer dereference happens whereas in C++,
because this paradigm
On 11/24/10 19:55, Avi Kivity wrote:
On 11/24/2010 08:10 PM, Gleb Natapov wrote:
On Wed, Nov 24, 2010 at 07:50:44PM +0200, Avi Kivity wrote:
On 11/24/2010 07:43 PM, Gleb Natapov wrote:
Implicit code means that you don't need to debug it. The
compiler
gets it right every time.
On 11/21/10 16:22, Anthony Liguori wrote:
On 11/14/2010 08:15 PM, Hidetoshi Seto wrote:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
On 11/18/10 01:41, Hidetoshi Seto wrote:
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
hw/virtio-9p-local.c:479: warning: implicit declaration of
On 11/18/10 09:48, Hidetoshi Seto wrote:
(2010/11/18 17:02), Jes Sorensen wrote:
Hi Hidetoshi,
I think the idea of the patch is good, but please move qemu_utimensat()
to oslib-posix.c and provide a wrapper for oslib-win32.c. It is
emulation for a system library function, so it doesn't belong
On 11/08/10 07:44, M. Mohan Kumar wrote:
This patch introduce a fallback mechanism for old systems that do not
support utimensat. This will fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
hw/virtio-9p-local.c:479: warning: implicit declaration
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
0.13 stable candidate?
ACK I would say so.
Jes
--
To unsubscribe from this list: send the line unsubscribe kvm in
the
On 10/03/10 10:58, Michael Tokarev wrote:
03.10.2010 02:08, KC8LDO wrote:
I've been watching this bug for a while now and I wonder why the
Fedora-13 distro doesn't seem to get the patch mentioned in the
following bug:
https://bugs.launchpad.net/qemu/+bug/586175 (see comment #29)
This
On 09/03/10 14:21, Michael Tokarev wrote:
Hello.
I noticed that window7, unlike windowsXP as I played with
previously, poses quite high load on host when idle. On
my machine, host cpu usage is about 25% when one single-cpu
win7 guest is running with -usbdevice tablet option.
Here's a
From: Jes Sorensen jes.soren...@redhat.com
Some operating systems store data about the host processor at the
time of installation, and when booted on a more uptodate cpu tries
to read MSR_EBC_FREQUENCY_ID. This has been found with XP.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
arch
On 09/09/10 10:12, Avi Kivity wrote:
From the spec:
31:24 Core Clock Frequency to System
Bus Frequency Ratio. (R)
The processor core clock
frequency to system bus
frequency ratio observed at the
de-assertion of the reset pin.
A frequency ratio of 0 might
On 09/09/10 10:29, Jes Sorensen wrote:
On 09/09/10 10:12, Avi Kivity wrote:
From the spec:
31:24 Core Clock Frequency to System
Bus Frequency Ratio. (R)
The processor core clock
frequency to system bus
frequency ratio observed at the
de-assertion of the reset
From: Jes Sorensen jes.soren...@redhat.com
Hi,
Discussed this with Juan and he spotted this place in
arch/x86/kernel/cpu/cpufreq/speedstep-lib.c which relies on the 'Core
Clock Frequency to System Bus Frequency Ratio', so leaving it set to 0
is not going to work. Reading the spec it also says
From: Jes Sorensen jes.soren...@redhat.com
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
arch/x86/include/asm/msr-index.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/include/asm/msr-index.h b/arch/x86/include/asm/msr-index.h
index 986f779..83c4bb1
From: Jes Sorensen jes.soren...@redhat.com
Some operating systems store data about the host processor at the
time of installation, and when booted on a more uptodate cpu tries
to read MSR_EBC_FREQUENCY_ID. This has been found with XP.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
arch
On 09/01/10 09:17, Avi Kivity wrote:
Less cluttered display.
Signed-off-by: Avi Kivity a...@redhat.com
---
kvm/kvm_stat |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kvm/kvm_stat b/kvm/kvm_stat
index 4a16277..d373c60 100755
--- a/kvm/kvm_stat
+++
On 08/31/10 22:02, Marcelo Tosatti wrote:
On Tue, Aug 31, 2010 at 06:33:34PM +0200, Jes Sorensen wrote:
which makes no sense to me, but given it's x86, I am not sure if it
could have come from the BIOS or something during reboot?
kvm_reset_msrs in qemu-kvm-x86.c.
Interesting, I hadn't
From: Jes Sorensen jes.soren...@redhat.com
This fix gets around the case where a user specifies a CPU model
triggering an old Opteron errata. The patch returns the clock timing
the errata expects to see and ignores writes to make sure a guest
doesn't get an exception from reading or writing
From: Jes Sorensen jes.soren...@redhat.com
MSR_K7_CLK_CTL is a no longer documented MSR, which is only relevant
on said old AMD CPU models. This change returns the expected value,
which the Linux kernel is expecting to avoid writing back the MSR,
plus it ignores all writes to the MSR.
Signed-off
On 08/18/10 08:12, Onkar Mahajan wrote:
Is there any benefit gained by porting 10Gb Ethernet adapters to
Qemu/KVM ? The question may be naive. Please forgive me if this doesn't
make any sense.
Creating a new QEMU driver to mimic one of the 10Gbit adapters is
probably a waste of time, you
From: Jes Sorensen jes.soren...@redhat.com
We regularly see bug reports over this one, however it is a write to
a read-only register which some operating systems (including Linux)
tend to write to once in a while.
Ignore the writes since they do no harm.
Signed-off-by: Jes Sorensen jes.soren
On 08/31/10 18:28, Avi Kivity wrote:
On 08/31/2010 03:17 PM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
We regularly see bug reports over this one, however it is a write to
a read-only register which some operating systems (including Linux)
tend to write to
On 08/31/10 18:44, Avi Kivity wrote:
On 08/31/2010 07:33 PM, Jes Sorensen wrote:
On 08/31/10 18:28, Avi Kivity wrote:
On 08/31/2010 03:17 PM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
We regularly see bug reports over this one, however it is a write
On 08/28/10 17:44, Martin Kraus wrote:
Hi. I'm trying to install windows 2008 on kvm running on debian squeeze with
qemu-kvm
0.12 but the installer complains about not being able to find any drivers for
the cdrom. Is there some way to feed it a cdrom driver? I've never had any
problems
On 08/30/10 14:45, Martin Kraus wrote:
By the installer I've meant the windows installer which complains that it
can't
find a driver for cdrom (emulated by kvm patched qemu). I can boot from the cd
image by using -drive file=.media=cdrom or -cdrom ... and the
installation starts but it
On 08/04/10 16:04, Gerrit van der Kolk wrote:
On Wed, 2010-08-04 at 14:53 +0200, Gerrit van der Kolk wrote:
I managed to get libvirtd out of the loop. I'm starting the vm with:
qemu-kvm -S -M fedora-13 -enable-kvm -m 2048 -smp
2,sockets=1,cores=2,threads=1 -name test -uuid
On 08/27/10 10:27, Jan Kiszka wrote:
Am 26.08.2010 22:06, jes.soren...@redhat.com wrote:
From: Jes Sorensen jes.soren...@redhat.com
Injecting an NMI while GUEST_INTR_STATE_STI is set may fail,
which can cause an EXIT with invalid state, resulting in the
guest dieing.
Very interesting
From: Jes Sorensen jes.soren...@redhat.com
Injecting an NMI while GUEST_INTR_STATE_STI is set may fail,
which can cause an EXIT with invalid state, resulting in the
guest dieing.
Credit to Gleb for figuring out why it was failing and how to
fix it.
v2: use vmcs_clear_bits() instead of vmcs_read
On 08/27/10 11:21, Avi Kivity wrote:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index cf56462..8e95371 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2888,6 +2888,8 @@ static void vmx_inject_nmi(struct kvm_vcpu *vcpu)
kvm_rip_write(vcpu, vmx-rmode.irq.rip -
On 08/27/10 11:47, Avi Kivity wrote:
On 08/27/2010 12:41 PM, Jes Sorensen wrote:
Ok, try v2 that I just posted - and forgot to add v2 in the Subject line
to - sorry.
Well, in light of Jan's comment re sti; hlt being clobbered by this, we
should think about requesting an interrupt window
On 08/27/10 11:59, Avi Kivity wrote:
On 08/27/2010 12:56 PM, Jes Sorensen wrote:
Well, in light of Jan's comment re sti; hlt being clobbered by this, we
should think about requesting an interrupt window instead...
Ok, I heading onto thin ice here :)
How does one do that, just a call
From: Jes Sorensen jes.soren...@redhat.com
In certain setups, especially with the RHEL5 kernel, the guest would
exit with an invalid state and die if one added nmi_watchdog=1 as a
kernel boot parameter.
Gleb gets the credit for the thinking, I just did the testing and
tracing on this one.
Jes
From: Jes Sorensen jes.soren...@redhat.com
Injecting an NMI while GUEST_INTR_STATE_STI is set may fail,
which can cause an EXIT with invalid state, resulting in the
guest dieing.
Credit to Gleb for figuring out why it was failing and how to
fix it.
Signed-off-by: Jes Sorensen jes.soren
From: Jes Sorensen jes.soren...@redhat.com
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the additional features are going to be available on
the host CPU.
Signed-off-by: Jes Sorensen
On 07/28/10 12:51, Avi Kivity wrote:
On 07/28/2010 01:05 PM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the
From: Jes Sorensen jes.soren...@redhat.com
This set of patches adds default CPU types to the PC compat
definitions, and patch #2 sets the CPU type to kvm64/kvm32 when
running under KVM.
Long term we might want to qdev'ify the CPUs but I think it is better
to keep it simple for 0.13.
Jes
From: Jes Sorensen jes.soren...@redhat.com
This allows for changing the default CPU type on the current PC
definition without breaking legacy mode.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
hw/boards.h |1 +
hw/pc_piix.c | 15 +++
vl.c |2 ++
3 files
From: Jes Sorensen jes.soren...@redhat.com
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the additional features are going to be available on
the host CPU.
Signed-off-by: Jes Sorensen
On 07/27/10 02:13, Alex Williamson wrote:
On Mon, 2010-07-26 at 18:28 -0500, Anthony Liguori wrote:
On 07/26/2010 05:28 PM, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the
On 07/24/10 17:04, Balachandar wrote:
On Fri, Jul 23, 2010 at 3:11 AM, Jes Sorensen jes.soren...@redhat.com wrote:
Actually i got better results when i downloaded qemu-kvm 0.12.4 from
sourceforge and ran it. Now virtio performs better than emaulated
e1000 with our own simple ping-pong latency
On 07/23/10 03:31, Balachandar wrote:
On Thu, Jul 22, 2010 at 8:18 PM, Sridhar Samudrala
I tried this one also but not much improvement. Actually i get a some
improvement if i disabled the tx timeout timer in the virtio_net.h in
qemu-kvm. I read that with vhost the data flow path differs from
Hi,
There has been some confusion around the format of the tracks at Linux
Plumbers: Presentations vs Micro Conference, so the program committee
has extended the deadline by one week. If you didn't get your submission
in earlier, or you were confused, this is your final chance.
Please see
re-submit it. I apologize for this confusion!
Hope to see plenty of proposals showing up before the deadling on the 19th!
Best regards,
Jes
On 06/18/10 14:00, Jes Sorensen wrote:
Hi,
I would like to remind people about the Virtualization track at Linux
Plumbers Conference 2010, held
On 07/01/10 16:38, Avi Kivity wrote:
On 06/30/2010 05:27 PM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
MSR_P6_EVNTSEL0 and MSR_P6_PERFCTR0 are used to probe for the P6 PMU
for older family 6 CPUs, which is also the default in QEMU. Ie. per
default we get the
On 07/01/10 16:44, Avi Kivity wrote:
On 07/01/2010 05:41 PM, Jes Sorensen wrote:
Saw it, which is why I only suggest we remove EVNTSEL0 and PERFCTR0 but
not the others. If the guest is expecting normal operation it is likely
to use more than just the first.
Why is that?
Depends
From: Jes Sorensen jes.soren...@redhat.com
MSR_P6_EVNTSEL0 and MSR_P6_PERFCTR0 are used to probe for the P6 PMU
for older family 6 CPUs, which is also the default in QEMU. Ie. per
default we get the noise of these warnings in dmesg, confusing users
for no reason.
Signed-off-by: Jes Sorensen
On 06/23/10 03:13, Zhang, Yanmin wrote:
On Tue, 2010-06-22 at 09:58 +0200, Jes Sorensen wrote:
Exposing the counters read-only would save a lot of overhead for sure.
Question is if it is safe to drop overflow support?
Not safe. One of PMU hardware design objectives is to use interrupt or NMI
On 06/22/10 03:49, Zhang, Yanmin wrote:
On Mon, 2010-06-21 at 14:45 +0300, Avi Kivity wrote:
Since the guest can use NMI to read the
counter, it should have the highest possible priority, and thus it
shouldn't see any overflow unless it configured the threshold really low.
If we drop
On 06/22/10 09:47, Zhang, Yanmin wrote:
On Tue, 2010-06-22 at 09:14 +0200, Jes Sorensen wrote:
On 06/22/10 03:49, Zhang, Yanmin wrote:
On Mon, 2010-06-21 at 14:45 +0300, Avi Kivity wrote:
So I think above discussion is around how to expose PMU hardware to guest
os. I will
also check
On 06/22/10 09:55, Peter Zijlstra wrote:
On Tue, 2010-06-22 at 15:47 +0800, Zhang, Yanmin wrote:
Besides the para virt perf interface, I'm also considering the direct
exposition
of PMU hardware to guest os.
NAK NAK NAK NAK, we've been over that, its not going to happen, full
stop!
Use
On 06/22/10 11:31, Peter Zijlstra wrote:
On Tue, 2010-06-22 at 17:29 +0800, Zhang, Yanmin wrote:
On Tue, 2010-06-22 at 10:00 +0200, Jes Sorensen wrote:
On 06/22/10 09:55, Peter Zijlstra wrote:
On Tue, 2010-06-22 at 15:47 +0800, Zhang, Yanmin wrote:
Besides the para virt perf interface, I'm
From: Jes Sorensen jes.soren...@redhat.com
This avoids breaking the build for non KVM targets where
kvm_set_irqfd() is not defined.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
hw/virtio-pci.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-pci.c
From: Jes Sorensen jes.soren...@redhat.com
Hi,
This set of patches fixes building qemu-kvm for non KVM targets, as
reported in
http://sourceforge.net/tracker/?func=detailatid=893831aid=2984626group_id=180599
One of the main problem is that we have a tendency to move things from
Makefile.objs
From: Jes Sorensen jes.soren...@redhat.com
Avoid build conflicts and move prototype out of CONFIG_KVM to make the
stub in kvm-stub.c visible.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
qemu-kvm.h | 29 -
1 files changed, 12 insertions(+), 17 deletions
From: Jes Sorensen jes.soren...@redhat.com
time_drift_fix is only present on x86, not just on !ia64. This allows
the code to build for other archs, like MIPS.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
hw/i8259.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
From: Jes Sorensen jes.soren...@redhat.com
pcspk.o i8254.o acpi.o acpi_piix4.o are all required for MIPS as well,
add them to Makefile.target accordingly.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
Makefile.target |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff
From: Jes Sorensen jes.soren...@redhat.com
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
qemu-kvm.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-kvm.h b/qemu-kvm.h
index c9b93dc..6dd3a01 100644
--- a/qemu-kvm.h
+++ b/qemu-kvm.h
@@ -835,6 +835,7 @@ void
From: Jes Sorensen jes.soren...@redhat.com
This fixes build breakage for target MIPS etc.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
vl.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/vl.c b/vl.c
index 0ee963c..79f91d5 100644
--- a/vl.c
+++ b/vl.c
From: Jes Sorensen jes.soren...@redhat.com
We need to declare 'int no_hpet' for all targets to avoid build
failure on no x86 builds.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
vl.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 79f91d5
On 06/22/10 15:23, Alexander Graf wrote:
Alex Williamson wrote:
Could we send the agenda note out a little bit earlier?
The note arrived at 12:55am CST and we decided we had no agenda at
7:04am CST. That's a pretty short window and I imagine a lot of people
in the US are not
Hi,
I would like to remind people about the Virtualization track at Linux
Plumbers Conference 2010, held in Cambridge, MA, November 3-5, 2010.
Please note the deadline for submissions is July 19, 2010.
LPC is particular well suited for technical presentations, work in
progress and subjects that
On 06/08/10 20:43, Gordan Bobic wrote:
Is this plausible?
I'm trying to work out if it's even worth considering this approach to
enable all memory used by in a system to be open to KSM page merging,
rather than only memory used by specific programs aware of it (e.g.
kvm/qemu).
Something
On 06/10/10 11:09, Gordan Bobic wrote:
On 06/10/2010 08:44 AM, Jes Sorensen wrote:
Not sure if it is worth it, but you might want to look at ElectricFence
which does malloc wrapping in a somewhat similar way. It might save you
some code :)
I'll look into it, but I don't see this requiring
On 05/31/10 09:46, Rusty Russell wrote:
On Thu, 27 May 2010 05:20:35 am Michael S. Tsirkin wrote:
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early
On 05/30/10 13:22, Michael S. Tsirkin wrote:
On Fri, May 28, 2010 at 11:56:54AM +0200, Jes Sorensen wrote:
It looks pretty good to me, however one thing I have been thinking of
while reading through it:
Rather than storing a pointer within the ring struct, pointing into a
position within
On 05/26/10 21:50, Michael S. Tsirkin wrote:
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early flames/comments.
Generally, the Host end of the
On 05/26/10 14:48, Avi Kivity wrote:
On 05/26/2010 03:27 AM, Juan Quintela wrote:
BTW, I also noticed the lack of pci_set_long() and friend functions, but
arrived to the same conclusion that you: all the device assignment
assumes that the world is x86_64 :)
IIRC it used to work on ia64
1 - 100 of 232 matches
Mail list logo
