On Tue, 2009-07-07 at 05:42 +0300, Cristi Magherusan wrote:
> Hi there,
>
> I'm trying to compile kvm using uClibc instead of glibc.
I upgraded to kvm-87 yesterday. It compiles, kvm is enabled, but guest
hangs when trying to mount the boot iso. I'm not sure if that I run kvm
in a vserver guest, o
On Sat, Jun 6, 2009 at 6:07 PM, Michael Goldish wrote:
> Try running cmd.exe (both under SSH and directly) and try running
> shutdown.exe there.
It does not work. I think there is something wrong with the environment.
> If that works, the problem is probably somewhere in the Cygwin configuration,
On Thursday 21 May 2009 06:25:17 Mark Langsdorf wrote:
> This feature creates a new field in the VMCB called Pause
> Filter Count. If Pause Filter Count is greater than 0 and
> intercepting PAUSEs is enabled, the processor will increment
> an internal counter when a PAUSE instruction occurs instea
I've been having some problem with recent releases when it comes to tap
initialization. It seems that the script is ran after the tap is opened. I
think this is a bit weird and useless as I want the script to setup the
tap by itself.
In net.c, the initialization (I assume) happen in
static
On 07/07/2009 09:48 PM, Stephane Bakhos wrote:
I've been having some problem with recent releases when it comes to
tap initialization. It seems that the script is ran after the tap is
opened. I think this is a bit weird and useless as I want the script
to setup the tap by itself.
In net.c, th
On 07/07/2009 11:53 PM, Daniel Gollub wrote:
On Tuesday 07 July 2009 09:47:29 pm Avi Kivity wrote:
[...]
If someone can help with setup, or even better, volunteer to setup and
host the buildmaster, we can concentrate more on patches and less on
breakage. Buildbot even has a 'try' command wh
On 07/08/2009 06:32 AM, Zhai, Edwin wrote:
/*
+ * Indicate a busy-waiting vcpu in spinlock. We do not enable the PAUSE
+ * exiting, so only get here on cpu with PAUSE-Loop-Exiting.
+ */
+static int handle_pause(struct kvm_vcpu *vcpu,
+ struct kvm_run *kvm_run)
+{
> ATM I will suggest to merge the patches in and let get tested so that
> we can collect failures/breakages if any.
I am not keen on causing regressions, which we've risked doing every
time we change LTP. I think we at least need to get a run on a non-virtualized
machine with some recent kernel, a
On 07/08/2009 01:23 AM, Stephen Donnelly wrote:
Also it appears that PCI IO memory (cpu_register_io_memory) is
provided via access functions, like the pci config space?
It can also use ordinary RAM (for example, vga maps its framebuffer as a PCI
BAR).
So host memory is exported
On Tue, Jul 7, 2009 at 9:01 PM, Lucas Meneghel Rodrigues wrote:
> On Tue, Jul 7, 2009 at 4:24 AM, sudhir kumar wrote:
>>> OK, Can we encapsulate this into the wrapper though, rather than making
>>> people do it manually? in the existing ltp.patch or something?
>>>
>> definitely we can do that, but
Ok Then. So my idea is to include the patch in autotest and let the
people report failures(in compilation or execution), and we can patch
autotest to apply the fix patch and build and run ltp. I do not think
we can find all cases untill and unless we start execution.
However I will start the discu
KVM:VMX: Add support for Pause-Loop Exiting
New NHM processors will support Pause-Loop Exiting by adding 2 VM-execution
control fields:
PLE_Gap- upper bound on the amount of time between two successive
executions of PAUSE in a loop.
PLE_Window - upper bound on the amount of time a
Folks, one more edition of our patch queue. Please let me know if you
have an unreviewed patch (hopefully we don't have any at this point :))
KVM test patch queue
Michael Goldish (mgold...@redhat.com)
1) KVM test: o
I've spent some time doing a second review and test of the code.
During my tests:
* I found some problems with PCI hotplug itself and would like help
to figure out why things are not working as expected.
* Made suggestions regarding the phrasing of the error messages
thrown by the test. Mostly n
Hi,
I created a VM (no guest OS installed yet) in my KVM box, and I can
run it normally.
But I found I can not reboot and shut down it by virt-manager, only
force shutdown works.
"Error shutting down domain: this function is not supported by the
hypervisor: virDomainReboot"
Any suggestions? Than
Avi Kivity wrote:
On 07/07/2009 05:58 PM, Jerry Geis wrote:
I thought so too, but in fact it emulates a 486sx+487. We can make
it emulate a 486sx without a 487, but that will take a kernel patch.
I'd be interested in that if you can make it happen.
I don't think I'll get around to it soon.
On Tue, Jul 07, 2009 at 10:00:25PM +0200, Peter Zijlstra wrote:
> It does feel slightly weird to explicitly overflow that preempt count
> though.
That is actually fixable there without adding more bits to preempt
count, just call a global preempt_disable after lockdep_off and call a
spinlock versi
On Mon, Jul 6, 2009 at 7:38 PM, Avi Kivity wrote:
>> I see virtio_pci uses cpu_physical_memory_map() which provides either
>> read or write mappings and notes "Use only for reads OR writes - not
>> for read-modify-write operations."
>
> Right, these are for unidirectional transient DMA.
Okay, as
Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
>> On Tue, Jul 07, 2009 at 05:31:25PM -0400, Masami Hiramatsu wrote:
>>> Frederic Weisbecker wrote:
On Tue, Jul 07, 2009 at 04:42:32PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
>> On Tue, Jul 07, 2009 at 03:55:28PM
Frederic Weisbecker wrote:
> On Tue, Jul 07, 2009 at 05:31:25PM -0400, Masami Hiramatsu wrote:
>> Frederic Weisbecker wrote:
>>> On Tue, Jul 07, 2009 at 04:42:32PM -0400, Masami Hiramatsu wrote:
Frederic Weisbecker wrote:
> On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
On Tue, Jul 07, 2009 at 05:31:25PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
> > On Tue, Jul 07, 2009 at 04:42:32PM -0400, Masami Hiramatsu wrote:
> >> Frederic Weisbecker wrote:
> >>> On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wro
An ioeventfd allows an eventfd to attach to a specific PIO/MMIO region in the
guest. Any guest-writes to that region will trigger an eventfd signal.
Signed-off-by: Gregory Haskins
---
libkvm-all.h | 44 +
qemu-kvm.c | 69 +++
This is the userspace-side patch to support ioeventfd. It compliments the
kernel-side patches (v10), published here:
http://lkml.org/lkml/2009/7/7/426
---
Gregory Haskins (1):
qemu-kvm: add ioeventfd support
libkvm-all.h | 44 +
qemu-kvm.c | 69
Howdy, developers of qemu, qemu-kvm, and libvirt. I periodically see
bug reports on these lists from users of Ubuntu packages of these
projects.
Since these users are often running some version of the project older
than the current development branch, it's more interesting to know if
the user can
Frederic Weisbecker wrote:
> On Tue, Jul 07, 2009 at 04:42:32PM -0400, Masami Hiramatsu wrote:
>> Frederic Weisbecker wrote:
>>> On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
Frederic Weisbecker wrote:
>> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
>> i
On Tuesday 07 July 2009 09:47:29 pm Avi Kivity wrote:
[...]
> If someone can help with setup, or even better, volunteer to setup and
> host the buildmaster, we can concentrate more on patches and less on
> breakage. Buildbot even has a 'try' command which lets submitters test
> patches.
I would v
ioeventfd is a mechanism to register PIO/MMIO regions to trigger an eventfd
signal when written to by a guest. Host userspace can register any
arbitrary IO address with a corresponding eventfd and then pass the eventfd
to a specific end-point of interest for handling.
Normal IO requires a blockin
Today kvm_io_bus_regsiter_dev() returns void and will internally BUG_ON
if it fails. We want to create dynamic MMIO/PIO entries driven from
userspace later in the series, so we need to enhance the code to be more
robust with the following changes:
1) Add a return value to the registration func
(Applies to kvm.git/master:3abaf217)
This is v10 of the series. For more details, please see the header to
patch 2/2.
This series has been tested against the kvm-eventfd unit test, and
appears to be functioning properly. You can download this test here:
ftp://ftp.novell.com/dev/ghaskins/kvm-ev
On Tue, Jul 07, 2009 at 04:42:32PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
> > On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
> >> Frederic Weisbecker wrote:
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index 206cb7d..65945eb 100644
>
Frederic Weisbecker wrote:
> On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
>> Frederic Weisbecker wrote:
diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
index 206cb7d..65945eb 100644
--- a/kernel/trace/trace.h
+++ b/kernel/trace/trace.h
@@ -45,6
On Tue, Jul 07, 2009 at 03:55:28PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
> >> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> >> index 206cb7d..65945eb 100644
> >> --- a/kernel/trace/trace.h
> >> +++ b/kernel/trace/trace.h
> >> @@ -45,6 +45,8 @@ enum trace_type {
>
On Tue, Jul 07, 2009 at 09:58:46AM +, Eran Rom wrote:
> Eran Rom il.ibm.com> writes:
>
> >
> > Eran Rom il.ibm.com> writes:
> >
> > Still getting a misbehaving clock:
> > guest uses kvmclock with kernel 2.6.27
> > host kernel is 2.6.27 with kvm-qemu-87 & kvm-kmod-87
> >
> > getting:
> > .
On Tue, 2009-07-07 at 12:25 -0700, Linus Torvalds wrote:
>
> On Tue, 7 Jul 2009, Peter Zijlstra wrote:
> >
> > Another issue, at about >=256 vmas we'll overflow the preempt count. So
> > disabling lockdep will only 'fix' this for a short while, until you've
> > bloated beyond that ;-)
>
> We wou
Frederic Weisbecker wrote:
>> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
>> index 206cb7d..65945eb 100644
>> --- a/kernel/trace/trace.h
>> +++ b/kernel/trace/trace.h
>> @@ -45,6 +45,8 @@ enum trace_type {
>> TRACE_POWER,
>> TRACE_BLK,
>> TRACE_KSYM,
>> +TRACE_KPROBE
On 07/07/2009 09:45 PM, Jan Kiszka wrote:
Also breaks --disable-kvm build. Avi, could you add a corresponding
build run with all targets enabled to your pre-commit tests?
I'd like to solve this in a more general way: buildbot. That will allow
testing a matrix of configs x host kernel x ho
On Tue, 7 Jul 2009, Peter Zijlstra wrote:
>
> Another issue, at about >=256 vmas we'll overflow the preempt count. So
> disabling lockdep will only 'fix' this for a short while, until you've
> bloated beyond that ;-)
We would?
I don't think so. Sure, we'd "overflow" into the softirq bits, but
On Tue, 2009-07-07 at 15:37 -0300, Marcelo Tosatti wrote:
> >>>
> >>> Is there any way around this other than completly shutting down lockdep?
> >>>
> >>
> >> When we created this the promise was that kvm would only do this on a
> >> fresh mm with only a few vmas, has that changed
> >
> > The
Andy Sy wrote:
I am trying to install Slackware on KVM-based
VPS hosting and keep getting a "LILO keytable read
/ checksum error" upon booting.
Grub-based distros install fine on said VPS.
Are you using virtio disks? It's probably that extboot doesn't
implement enough int13 functions for LIL
I've been having some problem with recent releases when it comes to tap
initialization. It seems that the script is ran after the tap is opened. I
think this is a bit weird and useless as I want the script to setup the
tap by itself.
In net.c, the initialization (I assume) happen in
static int
I am trying to install Slackware on KVM-based
VPS hosting and keep getting a "LILO keytable read
/ checksum error" upon booting.
Grub-based distros install fine on said VPS.
Apparently certain builds/versions of KVM break
with LILO:
http://kerneltrap.org/mailarchive/linux-kvm/2008/9/1/3152074/t
Avi Kivity wrote:
> On 07/06/2009 05:35 PM, Gleb Natapov wrote:
>> Old kernel assumed that apic id of a boot cpus is zero, recent kernels
>> have an IOCTL to configure BSP's apic id. The patch adds API function to
>> use this capability. The BSP apic id is set to zero (now explicitly)
>> since QEMU
Glauber Costa wrote:
> I just came across two errors in --disable-kvm builds.
>
> here's the patches to fix it.
Builds fine for me, too, resolving both issues I just reported.
Jan
signature.asc
Description: OpenPGP digital signature
On Tue, Jul 07, 2009 at 09:18:36PM +0300, Avi Kivity wrote:
> On 07/07/2009 09:15 PM, Peter Zijlstra wrote:
>> On Tue, 2009-07-07 at 15:06 -0300, Marcelo Tosatti wrote:
>>
>>> KVM guests with CONFIG_LOCKDEP=y trigger the following warning:
>>>
>>> BUG: MAX_LOCK_DEPTH too low!
>>> turning off th
Signed-off-by: Glauber Costa
---
hw/msix.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/hw/msix.c b/hw/msix.c
index b6f3948..8636f69 100644
--- a/hw/msix.c
+++ b/hw/msix.c
@@ -63,6 +63,7 @@
/* Flag for interrupt controller to declare MSI-X support */
in
otherwise, compilation breaks with kvm disabled.
Signed-off-by: Glauber Costa
---
hw/pc.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index cf84416..afab0ad 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -1131,7 +1131,9 @@ static void pc_init1(ram_addr_t
I just came across two errors in --disable-kvm builds.
here's the patches to fix it.
--
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
Avi Kivity wrote:
> On 07/05/2009 10:12 PM, Michael S. Tsirkin wrote:
>> Support msi-x with irqchip in kernel: allocate entries
>> when they are used, and update when they are unmasked.
>>
>
> Applied, thanks. I changed fprintf(r) to fprintf(strerror(-r)).
>
Breaks --disable-kvm build. Mich
On 07/07/2009 09:15 PM, Peter Zijlstra wrote:
On Tue, 2009-07-07 at 15:06 -0300, Marcelo Tosatti wrote:
KVM guests with CONFIG_LOCKDEP=y trigger the following warning:
BUG: MAX_LOCK_DEPTH too low!
turning off the locking correctness validator.
Pid: 4624, comm: qemu-system-x86 Not tainted 2.
On Tue, 2009-07-07 at 15:06 -0300, Marcelo Tosatti wrote:
> KVM guests with CONFIG_LOCKDEP=y trigger the following warning:
>
> BUG: MAX_LOCK_DEPTH too low!
> turning off the locking correctness validator.
> Pid: 4624, comm: qemu-system-x86 Not tainted 2.6.31-rc2-03981-g3abaf21
> #32
> Call Trace:
KVM guests with CONFIG_LOCKDEP=y trigger the following warning:
BUG: MAX_LOCK_DEPTH too low!
turning off the locking correctness validator.
Pid: 4624, comm: qemu-system-x86 Not tainted 2.6.31-rc2-03981-g3abaf21
#32
Call Trace:
[] __lock_acquire+0x1559/0x15fc
[] ? mm_take_all_locks+0x99/0x109
[
On Tue, Jul 7, 2009 at 12:24 AM, sudhir kumar wrote:
> On Tue, Jul 7, 2009 at 12:07 AM, Martin Bligh wrote:
Issues: LTP has a history of some of the testcases getting broken.
>>
>> Right, that's always the concern with doing this.
>>
Anyways
that has nothing to worry about with respe
Michael S. Tsirkin wrote:
> Looks good to me. One thing that's kind of ugly is the cleanup in i8254,
> see below. And a couple of other style comments.
>
> On Mon, Jul 06, 2009 at 04:33:15PM -0400, Gregory Haskins wrote:
>
>> Today kvm_io_bus_regsiter_dev() returns void and will internally BUG_O
On 07/07/2009 07:52 PM, Joerg Roedel wrote:
I would really like to have shadow 1GB work, or at least gain some
understanding of why it doesn't.
Can you detail the changes compared to the previous round?
Until now I addressed the review comments from the previous round. The
biggest change
On Tue, Jul 07, 2009 at 07:47:14PM +0300, Avi Kivity wrote:
> On 07/07/2009 07:41 PM, Joerg Roedel wrote:
> >Hi,
> >
> >this is the forth version of the patches for KVM to support 1GB pages.
> >This code still only can make use of 1GB pages with nested paging
> >enabled. I will give the shadow pagi
On 07/07/2009 07:41 PM, Joerg Roedel wrote:
Hi,
this is the forth version of the patches for KVM to support 1GB pages.
This code still only can make use of 1GB pages with nested paging
enabled. I will give the shadow paging code another debug round soon.
Please comment or consider to apply these
With the new name and the corresponding backend changes this function
can now support multiple hugepage sizes.
Signed-off-by: Joerg Roedel
---
arch/x86/kvm/mmu.c | 100 +--
arch/x86/kvm/paging_tmpl.h |4 +-
2 files changed, 69 insertions(+), 3
If userspace knows that the kernel part supports 1GB pages it can enable
the corresponding cpuid bit so that guests actually use GB pages.
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/kvm_host.h |2 ++
arch/x86/kvm/svm.c |6 ++
arch/x86/kvm/vmx.c |
Hi,
this is the forth version of the patches for KVM to support 1GB pages.
This code still only can make use of 1GB pages with nested paging
enabled. I will give the shadow paging code another debug round soon.
Please comment or consider to apply these patches.
Thanks,
Joerg
sho
The page walker may be used with nested paging too when accessing mmio
areas. Make it support the additional page-level too.
Signed-off-by: Joerg Roedel
---
arch/x86/kvm/mmu.c | 13 +++
arch/x86/kvm/paging_tmpl.h | 52 +++
2 files chan
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/kvm_host.h |2 +-
arch/x86/kvm/mmu.c | 74 ++
arch/x86/kvm/paging_tmpl.h |6 ++--
3 files changed, 47 insertions(+), 35 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b
This patch removes the largepage parameter from the rmap_add function.
Together with rmap_remove this function now uses the role.level field to
find determine if the page is a huge page.
Signed-off-by: Joerg Roedel
---
arch/x86/kvm/mmu.c | 53 +++
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/kvm_host.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index 1fa1ff0..be2315b 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/as
On Wed, 2009-07-01 at 17:17 -0700, Eric W. Biederman wrote:
> Suresh Siddha writes:
> > Among number of experiments you have tried in the past to fix this, have
> > you tried the experiment of explicitly clearing the remoteIRR by
> > changing the trigger mode to edge and then back to level.
> >
>
On Tue, 2009-07-07 at 10:31 -0500, Javier Guerra wrote:
> On Tue, Jul 7, 2009 at 6:31 AM, Cristi
> Magherusan wrote:
> > The kernel will be 2.6.24 because it's smaller. I know this mismatch may
> > not be good, but I have to get to a compromise. The kernel needs to be
> > as small as possible (ever
When kvm is in hpet_legacy_mode, the hpet is providing the
timer interrupt and the pit should not be. So in legacy mode, the pit timer is
destroyed, but the *state* of the pit is maintained. So if kvm or the guest
tries to modify the state of the pit, this modification is accepted, *except*
that
Select irq0->irq2 override based on kernel gsi routing availability
If the kernel does not support gsi routing, we cannot do the irq0->irq2
override, so disable it in that case.
Signed-off-by: Beth Kon
Signed-off-by: Avi Kivity
---
hw/ioapic.c|6 +++---
hw/pc.c
The big change here is handling of enabling/disabling of hpet legacy mode. When
hpet enters
legacy mode, the spec says that the pit stops generating interrupts. In
practice, we want to
stop the pit periodic timer from running because it is wasteful in a virtual
environment.
We also have to worr
Advertise HPET in ACPI HPET table
Signed-off-by: Beth Kon
Signed-off-by: Avi Kivity
---
kvm/bios/acpi-dsdt.dsl |2 --
kvm/bios/rombios32.c | 11 +++
2 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/kvm/bios/acpi-dsdt.dsl b/kvm/bios/acpi-dsdt.dsl
index
bios: allow qemu to configure irq0->inti2 override
Win2k8 expects the HPET interrupt on inti2, regardless of whether
an override exists in the BIOS. And the HPET spec states that in legacy
mode,
timer interrupt is on inti2.
The irq0->inti2 override will always be used unless
On 07/07/2009 03:27 PM, Gleb Natapov wrote:
This will save a couple of IPIs.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majord
On 07/07/2009 05:58 PM, Jerry Geis wrote:
I thought so too, but in fact it emulates a 486sx+487. We can make
it emulate a 486sx without a 487, but that will take a kernel patch.
I'd be interested in that if you can make it happen.
I don't think I'll get around to it soon. I'll happily apply
On Tue, Jul 7, 2009 at 4:24 AM, sudhir kumar wrote:
>> OK, Can we encapsulate this into the wrapper though, rather than making
>> people do it manually? in the existing ltp.patch or something?
>>
> definitely we can do that, but that needs to know about all the corner
> cases of failure. So may be
On Tue, Jul 7, 2009 at 6:31 AM, Cristi
Magherusan wrote:
> The kernel will be 2.6.24 because it's smaller. I know this mismatch may
> not be good, but I have to get to a compromise. The kernel needs to be
> as small as possible (everything should fit in a 4MB BIOS flash)
i know it's a big change;
On Tue, Jul 07, 2009 at 11:12:44PM +0800, Zhang Qian wrote:
> Hi,
>
> I'd like to know if virDomainSetSchedulerParameters() works for KVM
> domain, I want to set CPU weight for a KVM domain, is it possible?
> Thanks a lot!
The API you're asking about is not actually a KVM one, rather a libvirt
AP
Hi,
I'd like to know if virDomainSetSchedulerParameters() works for KVM
domain, I want to set CPU weight for a KVM domain, is it possible?
Thanks a lot!
Regards,
Qian
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majo
Avi Kivity wrote:
On 07/07/2009 04:15 PM, Jerry Geis wrote:
Notice FPU indicates yes and I requested -fpu on the command line.
I think it detects the host fpu as a 487 coprocessor. Anything in
dmesg about it? Note there's no fpu in the flags: line.
That's a kvm kernel bug.
also is this
ACK
On Tue, Jul 07, 2009 at 03:27:32PM +0300, Gleb Natapov wrote:
> This will save a couple of IPIs.
>
> Signed-off-by: Gleb Natapov
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index efb0b68..1e30400 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -3498,6 +3498,7 @
On Tuesday 07 July 2009 07:31:30 Cristi Magherusan wrote:
> On Tue, 2009-07-07 at 12:12 +0300, Avi Kivity wrote:
> > On 07/07/2009 05:42 AM, Cristi Magherusan wrote:
> > > I'm using linux-2.6.26.8, uClibc-HEAD(linuxthreds, almost complete
> > > setup) and gcc 4.3.3.
> > >
> > > Also, is this kernel
On Tuesday 07 July 2009 03:34:57 Bernhard Reutner-Fischer wrote:
> On Mon, Jul 06, 2009 at 11:21:03PM -0400, Mike Frysinger wrote:
> >On Monday 06 July 2009 22:42:46 Cristi Magherusan wrote:
> >> /home/cristi/devel/avatt/buildroot/build_i586/kvm-87/qemu-kvm-x86.c:1538
> >>: undefined reference to `
Bugs item #2817367, was opened at 2009-07-06 04:33
Message generated for change (Comment added) made by perlstalker
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2817367&group_id=180599
Please note that this message will contain a full copy of the comme
On 07/07/2009 04:00 PM, Gleb Natapov wrote:
Add tracepoint in msi/ioapic/pic set_irq() functions,
in IPI sending and in the point where IRQ is placed into
apic's IRR.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the
Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2009 at 08:56:43AM -0400, Gregory Haskins wrote:
>
>> Michael S. Tsirkin wrote:
>>
>>> On Tue, Jul 07, 2009 at 03:27:49PM +0300, Avi Kivity wrote:
>>>
>>>
On 07/07/2009 03:22 PM, Michael S. Tsirkin wrote:
>>>
On Tue, Jul 07, 2009 at 08:56:43AM -0400, Gregory Haskins wrote:
> Michael S. Tsirkin wrote:
> > On Tue, Jul 07, 2009 at 03:27:49PM +0300, Avi Kivity wrote:
> >
> >> On 07/07/2009 03:22 PM, Michael S. Tsirkin wrote:
> >>
> >>> On Tue, Jul 07, 2009 at 02:53:18PM +0300, Avi Kivity wrote:
> >>
On 07/07/2009 04:15 PM, Jerry Geis wrote:
Notice FPU indicates yes and I requested -fpu on the command line.
I think it detects the host fpu as a 487 coprocessor. Anything in
dmesg about it? Note there's no fpu in the flags: line.
That's a kvm kernel bug.
also is this a 486 as it says AM
Avi Kivity wrote:
> (adding Davide, there's a small comment for you in the middle, search
> for eventfd)
>
> On 07/07/2009 02:20 PM, Michael S. Tsirkin wrote:
>>
>>> @@ -307,6 +307,19 @@ struct kvm_guest_debug {
>>> struct kvm_guest_debug_arch arch;
>>> };
>>>
>>> +#define KVM_IOSIGNALFD_FL
Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2009 at 08:15:08AM -0400, Gregory Haskins wrote:
>
>> Michael S. Tsirkin wrote:
>>
>>> Some comments below. Sorry, I know it's late in the series, but
>>> previously I've been too confused with complicated locking to notice
>>> anything else :(.
>
Avi Kivity wrote:
On 07/07/2009 03:36 PM, Jerry Geis wrote:
Avi Kivity wrote:
On 07/07/2009 03:06 PM, Jerry Geis wrote:
Try -cpu 486,-fpu.
Avi,
Running this command:
qemu-system-x86_64 -net nic,model=rtl8139 -net user -hda $1
-no-acpi -usb -cpu 486,-fpu &
I get a seg fault:
qemu-syst
Add tracepoint in msi/ioapic/pic set_irq() functions,
in IPI sending and in the point where IRQ is placed into
apic's IRR.
Signed-off-by: Gleb Natapov
---
The difference from previous version are:
int -> bool for coalesced parameter.
no "=" in output.
addr in msi irq trace is u64 now.
diff -
On 07/07/2009 03:36 PM, Jerry Geis wrote:
Avi Kivity wrote:
On 07/07/2009 03:06 PM, Jerry Geis wrote:
Try -cpu 486,-fpu.
Avi,
Running this command:
qemu-system-x86_64 -net nic,model=rtl8139 -net user -hda $1 -no-acpi
-usb -cpu 486,-fpu &
I get a seg fault:
qemu-system-x86[15419]: segfau
On Tue, Jul 07, 2009 at 03:56:09PM +0300, Avi Kivity wrote:
> On 07/07/2009 03:48 PM, Michael S. Tsirkin wrote:
> +
> + __kvm_io_bus_unregister_dev(bus,&p->dev);
> + iosignalfd_release(p);
>
>
a single deassign removed multiple irqfds? Looks ugly.
Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2009 at 03:27:49PM +0300, Avi Kivity wrote:
>
>> On 07/07/2009 03:22 PM, Michael S. Tsirkin wrote:
>>
>>> On Tue, Jul 07, 2009 at 02:53:18PM +0300, Avi Kivity wrote:
>>>
>>>
>> +/* address-range must be precise for a
On 07/07/2009 03:51 PM, Michael S. Tsirkin wrote:
Seriously, why add artificial limitations?
IMO, addr=0,len=1 and addr=0,len=2 should not conflict.
They should not conflict, but a two byte write need not hit a one byte
registration.
Yes. That's exactly what I'm saying. I thi
On 07/07/2009 03:48 PM, Michael S. Tsirkin wrote:
+
+ __kvm_io_bus_unregister_dev(bus,&p->dev);
+ iosignalfd_release(p);
a single deassign removed multiple irqfds? Looks ugly.
Avi requested this general concept.
Really? Avi, could you expl
On Tue, Jul 07, 2009 at 03:27:49PM +0300, Avi Kivity wrote:
> On 07/07/2009 03:22 PM, Michael S. Tsirkin wrote:
>> On Tue, Jul 07, 2009 at 02:53:18PM +0300, Avi Kivity wrote:
>>
> + /* address-range must be precise for a hit */
>
>
So there's apparently no way
On 07/07/2009 03:44 PM, Gleb Natapov wrote:
On Tue, Jul 07, 2009 at 01:06:00PM +0300, Avi Kivity wrote:
On 07/06/2009 04:17 PM, Gleb Natapov wrote:
Add tracepoint in msi/ioapic/pic set_irq() functions,
in IPI sending and in the point where IRQ is placed into
apic's IRR.
Signed-off-by
On Tue, Jul 07, 2009 at 08:15:08AM -0400, Gregory Haskins wrote:
> Michael S. Tsirkin wrote:
> > Some comments below. Sorry, I know it's late in the series, but
> > previously I've been too confused with complicated locking to notice
> > anything else :(.
> >
> > On Mon, Jul 06, 2009 at 04:33:21PM
On Tue, Jul 07, 2009 at 01:06:00PM +0300, Avi Kivity wrote:
> On 07/06/2009 04:17 PM, Gleb Natapov wrote:
>> Add tracepoint in msi/ioapic/pic set_irq() functions,
>> in IPI sending and in the point where IRQ is placed into
>> apic's IRR.
>>
>> Signed-off-by: Gleb Natapov
>> diff --git a/arch/x86/kv
Avi Kivity wrote:
On 07/07/2009 03:06 PM, Jerry Geis wrote:
Try -cpu 486,-fpu.
Avi,
Running this command:
qemu-system-x86_64 -net nic,model=rtl8139 -net user -hda $1 -no-acpi
-usb -cpu 486,-fpu &
I get a seg fault:
qemu-system-x86[15419]: segfault at c ip 00458b95 sp
41d
Avi Kivity wrote:
On 07/07/2009 03:06 PM, Jerry Geis wrote:
Try -cpu 486,-fpu.
Avi,
Running this command:
qemu-system-x86_64 -net nic,model=rtl8139 -net user -hda $1 -no-acpi
-usb -cpu 486,-fpu &
I get a seg fault:
qemu-system-x86[15419]: segfault at c ip 00458b95 sp
41d9
1 - 100 of 135 matches
Mail list logo
