- kvm_hugepages variant enables us to test if (host) kvm use of
hugepages works
- libhugetlbfs test inside of guest prove, that (guest) system is able
to handle hugepages (independently of whether guest uses hugepages).
This function is necessarily eg. if you want to run Oracle server inside
th
> +Event Profiling
> +---
> + You can check the total number of probe hits and probe miss-hits via
> +/sys/kernel/debug/tracing/kprobe_profile.
> + The fist column is event name, the second is the number of probe hits,
s/fist/first
> +the third is the number of probe miss-hits.
> +
>
Why do you want to use a control file and put the libhugetlbfs as a
variant of autotest in kvm? Just keeping the kvm_hugepages variant
will not serve the same purpose ? I have been using hugetlbfs variant
for a long but yes without pre script(I have done that manually)? Am I
missing something here?
Subash Kalbarga wrote:
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Subash Kalbarga
> Sent: Thursday, July 09, 2009 12:51 PM
> To: kvm@vger.kernel.org
> Subject:
>
> Hi
>
> I find that the HOW-TO for VT-d pass through on linux-kv
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> I didn't know this was possible... so we could also use this driver for
> vm-channel.
With MSI things are much nicer (which we could define for vm-channel).
This is for shared legacy INTx.
>> +
>> +err = pci_request_regions(pdev, "uio_pci_
* Michael S. Tsirkin (m...@redhat.com) wrote:
> +struct generic_dev {
I know I commented on this one on an earlier, private version, and naming
is not my strength... maybe "struct uio_generic_pci_dev" or "struct
uio_generic_pci"?
> + struct uio_info info;
> + struct pci_dev *pdev;
> +
On 07/08/2009 09:51 AM, Lucas Meneghel Rodrigues wrote:
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
Anthony Liguori writes:
> Mark McLoughlin wrote:
>> Hi Anthony,
>>
>> On Mon, 2009-06-22 at 18:57 -0500, Anthony Liguori wrote:
>>
>>> Hi,
>>>
>>> It's getting to be about the time to start thinking about the
>>> 0.11.0 release. 0.10.0 was released on March 2nd so following with
>>> the 6 mon
On Thu, Jul 9, 2009 at 6:01 PM, Cam Macdonell wrote:
>> Is there a corresponding qemu patch for the backend to the guest pci
>> driver?
>
> Oops right. For some reason I can't my driver patch in patchwork.
>
> http://kerneltrap.org/mailarchive/linux-kvm/2009/5/7/5665734
Thanks for the link, I h
On Thu, Jul 09, 2009 at 03:14:53PM -0500, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>> On Thu, Jul 09, 2009 at 09:54:43AM -0500, Anthony Liguori wrote:
>>
>>> I know it's not strictly needed for PCI pass through, but it would be
>>> useful to register the IO regions via UIO. The user
Support up to 128 arguments for each kprobes event.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Christoph Hellwig
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Tom Zanussi
---
Documentation/trace/kprobetrace.txt |2 +-
kernel/trace/trace_kprobe.
Hi,
Here are the v11 patches. I updated it for the latest -tip and
add some features.
Here are the patches of kprobe-based event tracer for x86, version 11,
which allows you to probe various kernel events through ftrace interface.
The tracer supports per-probe filtering which allows you to set fi
Add profiling interaces for each kprobes event.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Christoph Hellwig
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Tom Zanussi
---
Documentation/trace/kprobetrace.txt |8 ++
kernel/trace/trace_kprobe.
Add kprobes-based event tracer on ftrace.
This tracer is similar to the events tracer which is based on Tracepoint
infrastructure. Instead of Tracepoint, this tracer is based on kprobes
(kprobe and kretprobe). It probes anywhere where kprobes can probe(this
means, all functions body except for __
Generate names for each kprobe event based on the probe point,
and remove generic k*probe event types because there is no user
of those types.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Christoph Hellwig
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: T
Add a user-space selftest of x86 instruction decoder at kernel build time.
When CONFIG_X86_DECODER_SELFTEST=y, Kbuild builds a test harness of x86
instruction decoder and performs it after building vmlinux.
The test compares the results of objdump and x86 instruction decoder
code and check there ar
Add following APIs for accessing registers and stack entries from pt_regs.
These APIs are required by kprobes-based event tracer on ftrace.
Some other debugging tools might be able to use it too.
- regs_query_register_offset(const char *name)
Query the offset of "name" register.
- regs_query_r
Use TRACE_FIELD_ZERO(type, item) instead of TRACE_FIELD_ZERO_CHAR(item).
This also includes a fix of TRACE_ZERO_CHAR() macro.
Signed-off-by: Masami Hiramatsu
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Tom Zanussi
Cc: Frederic Weisbecker
---
kernel/trace/trace_event_types.h |4 ++--
kernel/t
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode x86 instructions used in kernel into prefix, opcode, modrm,
sib, displacement and immediates. This can also show the length of
instructions.
This version introduces instruction attributes for decoding instructions.
The
Cleanup fix_riprel() in arch/x86/kernel/kprobes.c by using x86 instruction
decoder.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo Molnar
---
arch/x86/kernel/kprobes.c | 128 -
1 files changed, 23 insertio
Add dynamic ftrace_event_call support to ftrace. Trace engines can adds new
ftrace_event_call to ftrace on the fly. Each operator functions of the call
takes a ftrace_event_call data structure as an argument, because these
functions may be shared among several ftrace_event_calls.
Signed-off-by: Ma
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction on x86.
This is done by decoding probed function from its head to the probe point.
Signed-off-by: Masami Hiramatsu
Acked-by: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo
Michael S. Tsirkin wrote:
On Thu, Jul 09, 2009 at 09:54:43AM -0500, Anthony Liguori wrote:
I know it's not strictly needed for PCI pass through, but it would be
useful to register the IO regions via UIO. The userspace implementation
would then use UIO strictly instead of poking the sysfs
On 09.07.2009, at 20:22, Fischer, Anna wrote:
Subject: Re: KVM for Linux 2.6.16?
On Thu, 2009-07-09 at 16:49 +, Fischer, Anna wrote:
Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I
thought that it has been back-ported to such an old kernel.
However, I
don't seem to be
Luiz Capitulino wrote:
On Sun, 5 Jul 2009 15:58:23 +0300
"Michael S. Tsirkin" wrote:
This fixes segfault reported by Kevin Wolf,
and simplifies the code in msix_save.
Reported-by: Kevin Wolf
Signed-off-by: Michael S. Tsirkin
Any reason on why this wasn't applied yet?
Spent some
On Sun, 5 Jul 2009 15:58:23 +0300
"Michael S. Tsirkin" wrote:
> This fixes segfault reported by Kevin Wolf,
> and simplifies the code in msix_save.
>
> Reported-by: Kevin Wolf
> Signed-off-by: Michael S. Tsirkin
Any reason on why this wasn't applied yet?
Spent some time bisecting this just
Not worth respinning for, but if you do generate v11
On Tue, Jul 07, 2009 at 05:08:49PM -0400, Gregory Haskins wrote:
> 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 c
Not worth respinning for, but if you do generate v11 ...
On Tue, Jul 07, 2009 at 05:08:44PM -0400, Gregory Haskins wrote:
> 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
> Subject: Re: KVM for Linux 2.6.16?
>
> On Thu, 2009-07-09 at 16:49 +, Fischer, Anna wrote:
> > Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I
> thought that it has been back-ported to such an old kernel. However, I
> don't seem to be able to compile the module on my kernel.
Resending with corrected addresses. Sorry about the churn.
---
I got annoyed by the fact that we don't support shared interrupts
with PCI in assigned devides, so here's a draft patch to add that
support in kernel through uio.
I intend to send this to lkml, but meanwhile I'd appreciate s
On Sun, Apr 05, 2009 at 03:12:04PM +0300, Avi Kivity wrote:
> Avi Kivity wrote:
>>> I think all the settings should be reset to 0
>>> when opening the tun device.
>>
>> This should definitely be fixed. I'll look at writing a patch.
>>
>
> Okay, that's not in upstream qemu, so I committed a fix to
On Thu, Jul 09, 2009 at 09:54:43AM -0500, Anthony Liguori wrote:
> I know it's not strictly needed for PCI pass through, but it would be
> useful to register the IO regions via UIO. The userspace implementation
> would then use UIO strictly instead of poking the sysfs pci info
> directly. I
>> Timing with the rotational stuff set to 1...
>>
>> real14m13.015s
>> user29m42.162s
>> sys 8m37.416s
>
> (user + sys) / real = 2.7
>
>> And finally, to confirm the numbers on the host with no guest running...
>> The same disk/filesystem, now mounted on the host instead of the guest,
On Thu, 2009-07-09 at 11:20 +0300, Avi Kivity wrote:
> On 07/08/2009 08:34 PM, Cristi Magherusan wrote:
> > Also, what is extboot used for?
>
> Booting a guest from virtio and scsi.
>
> > Can I ommit it from my build?
> >
>
> If you like. It's only a handful of bytes though.
Hi Avi,
I aske
On Thu, 2009-07-09 at 16:49 +, Fischer, Anna wrote:
> Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I thought that
> it has been back-ported to such an old kernel. However, I don't seem to be
> able to compile the module on my kernel. I get the following error:
>
> CCt
On 09.07.2009, at 18:49, Fischer, Anna wrote:
Is KVM not supposed to work on 2.6.16?
May I ask for the reason you want to run KVM on such an old kernel and
even compile it yourself? :-)
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to maj
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Subash Kalbarga
Sent: Thursday, July 09, 2009 12:51 PM
To: kvm@vger.kernel.org
Subject:
Hi
I find that the HOW-TO for VT-d pass through on linux-kvm.org asks for
Interrupt Remapping to be
Hi
I find that the HOW-TO for VT-d pass through on linux-kvm.org asks for
Interrupt Remapping to be enabled in the kernel. However Interrupt
Remapping is dependent on x86_64 (DMAR was also dependent but I guess
the 2.6.30 kernel allows it for 32 bit systems)
Does that mean I will not be able to t
Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I thought that
it has been back-ported to such an old kernel. However, I don't seem to be able
to compile the module on my kernel. I get the following error:
CCtsc2005.o
CCscsi-disk.o
CCcdrom.o
CCscsi-generic.
Michael S. Tsirkin wrote:
Resending with corrected addresses. Sorry about the churn.
---
I got annoyed by the fact that we don't support shared interrupts
with PCI in assigned devides, so here's a draft patch to add that
support in kernel through uio.
I intend to send this to lkml, but
Gregory Haskins wrote:
> 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
Signed-off-by: Joerg Roedel
---
arch/x86/kvm/mmu.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 231d880..7162651 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -1786,8 +1786,8 @@ static void mmu_set_spte(str
On Tue, Jul 07, 2009 at 05:08:38PM -0400, Gregory Haskins wrote:
> (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 proper
Mark McLoughlin wrote:
Hi Anthony,
On Mon, 2009-06-22 at 18:57 -0500, Anthony Liguori wrote:
Hi,
It's getting to be about the time to start thinking about the 0.11.0
release. 0.10.0 was released on March 2nd so following with the 6 month
release cycle, that would put 0.11.0 at September
Change it from list to array to make RCU handling simpler.
Signed-off-by: Gleb Natapov
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index f54a0d3..12d8d2b 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -161,7 +161,8 @@ struct kvm {
struct mut
On Tue, Jul 07, 2009 at 02:36:31PM -0400, Glauber Costa wrote:
> 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
>
Hi Michael,
actually it's necessarily. qemu-kvm only put this message into the
output and continue booting the guest without hugepage support. Autotest
than runs all the test. Later in the output is no mention about this.
You have to predict that this happend and look at debug output of all
p
On Thu, 9 Jul 2009 03:42:20 am Christoph Hellwig wrote:
> On Tue, Jun 23, 2009 at 04:43:10PM +0930, Rusty Russell wrote:
> > On Sun, 21 Jun 2009 04:59:41 am Christoph Hellwig wrote:
> > > Block driver ioctl methods must return ENOTTY and not -ENOIOCTLCMD if
> > > they expect the block layer to hand
Remove kvm_cpu_has_interrupt() and kvm_arch_interrupt_allowed() from
interface between general code and arch code. kvm_arch_vcpu_runnable()
checks for interrupts instead.
Signed-off-by: Gleb Natapov
---
arch/ia64/kvm/kvm-ia64.c| 16 ++--
arch/powerpc/kvm/powerpc.c |
Signed-off-by: Gleb Natapov
---
arch/x86/kvm/x86.c | 21 +
1 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index e3d9040..de73e7c 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -223,13 +223,6 @@ void kvm_q
Move it from global .h file to arch/x86
Signed-off-by: Gleb Natapov
---
arch/x86/include/asm/kvm_host.h |1 +
include/linux/kvm_host.h|1 -
2 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 bbc97
Signed-off-by: Gleb Natapov
---
arch/ia64/kvm/kvm-ia64.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/ia64/kvm/kvm-ia64.c b/arch/ia64/kvm/kvm-ia64.c
index 421c3a4..0ad09f0 100644
--- a/arch/ia64/kvm/kvm-ia64.c
+++ b/arch/ia64/kvm/kvm-ia64.c
@@ -985,10 +985,10
I don't think you need to explicitly check for a memory allocation
failure in VM.create() ("qemu produced some output ...").
VM.create() already makes sure the VM is started successfully, and
prints informative failure messages if there's any problem.
- "Lukáš Doktor" wrote:
> This patch add
Resending with corrected addresses. Sorry about the churn.
---
I got annoyed by the fact that we don't support shared interrupts
with PCI in assigned devides, so here's a draft patch to add that
support in kernel through uio.
I intend to send this to lkml, but meanwhile I'd appreciate so
I got annoyed by the fact that we don't support shared interrupts
with PCI in assigned devides, so here's a draft patch to add that
support in kernel through uio.
I intend to send this to lkml, but meanwhile I'd appreciate some early
feedback/flames from people on the list.
Thanks!
--->
Set English environment before test executions.
This is critical because we are parsing outputs of commands, which are
localized!
Tested by: ldok...@redhat.com on RHEL5.4 with kvm-83-72.el5
--- orig/client/tests/kvm/control 2009-07-08 13:18:07.0 +0200
+++ new/client/tests/kvm/cont
On 07/09/2009 01:41 AM, Brian Jackson wrote:
I tried doing the email confirmation on the wiki so I could be emailed on page
changes, etc. Every time I hit the "Mail a confirmation code" button it says:
"Could not send confirmation mail. Check address for invalid characters."
I've re-entered my
This patch adds kvm_hugepage variant. It prepares the host system and
start vm with -mem-path option. It does not clean after itself, because
it's impossible to unmount and free hugepages before all guests are
destroyed.
There is also added autotest.libhugetlbfs test.
I need to ask you what t
set_cr3() should already cover the TLB flushing.
Signed-off-by: Sheng Yang
---
arch/x86/kvm/mmu.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 231d880..501c11e 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -
Hi Anthony,
On Mon, 2009-06-22 at 18:57 -0500, Anthony Liguori wrote:
> Hi,
>
> It's getting to be about the time to start thinking about the 0.11.0
> release. 0.10.0 was released on March 2nd so following with the 6 month
> release cycle, that would put 0.11.0 at September 2nd.
>
> Based on
On 07/08/2009 08:34 PM, Cristi Magherusan wrote:
Also, what is extboot used for?
Booting a guest from virtio and scsi.
Can I ommit it from my build?
If you like. It's only a handful of bytes though.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from
On 07/09/2009 12:33 AM, Stephen Donnelly wrote:
Shared memory is fully coherent. You can use the ordinary x86 bus lock
operations for concurrent read-modify-write access, and the memory barrier
instructions to prevent reordering. Just like ordinary shared memory.
Okay, I think I was con
On 07/09/2009 05:36 AM, Erik Jacobson wrote:
Haven't followed the thread in great detail, but has anyone tried
putting the virtio disk back into rotational mode?
Hello. I haven't had a chance to try all the suggestions in the thread
so far. However, I did just run some tests with block
63 matches
Mail list logo
