Bugs item #2976863, was opened at 2010-03-26 14:44
Message generated for change (Tracker Item Submitted) made by haoxudong
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2976863&group_id=180599
Please note that this message will contain a full copy of th
It's only in qemu-kvm.git. Maybe it should go into qemu-kvm-0.12.4 if
there is one
Sent from my iPhone
On Mar 25, 2010, at 9:37 PM, Kenni Lund wrote:
2010/1/9 Alexander Graf :
On 09.01.2010, at 03:45, Ryan C. Underwood wrote:
I have a multifunction PCI device that I'd like to pass thro
Lucas Meneghel Rodrigues wrote:
On Wed, Mar 24, 2010 at 2:59 AM, Jason Wang wrote:
Lucas Meneghel Rodrigues wrote:
On Mon, Mar 22, 2010 at 4:45 AM, Jason Wang wrote:
TSC is used to check the whether the TSC of processors are
synchronized which is useful for testing virtual TS
2010/1/9 Alexander Graf :
>
> On 09.01.2010, at 03:45, Ryan C. Underwood wrote:
>
>>
>> I have a multifunction PCI device that I'd like to pass through to KVM.
>> In order to do that, I'm reading that the PCI memory region must be 4K-page
>> aligned and the PCI memory resources itself must also be
Avi Kivity wrote:
> On 03/22/2010 11:13 AM, Sheng Yang wrote:
>>
>>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>>> index 06108f3..f971b9b 100644
>>> --- a/arch/x86/kvm/vmx.c
>>> +++ b/arch/x86/kvm/vmx.c
>>> @@ -1804,9 +1804,15 @@ static u64 construct_eptp(unsigned long root_hpa)
>>> {
Cam Macdonell wrote:
> An irqfd can only trigger a single vector in a guest. Right now I
> only have one eventfd per guest.So ioeventfd/irqfd restricts the
> current implementation to a single vector that a guest can trigger.
> Without irqfd, eventfds can be used like registers a write the num
On Thu, Mar 25, 2010 at 3:10 PM, Avi Kivity wrote:
> On 03/25/2010 08:17 PM, Cam Macdonell wrote:
>>
I had a hunch it was probably considered. That explains why irqfd
doesn't have a datamatch field. I guess supporting multiple MSI
vectors with one doorbell per guest isn't possible
Am 25.03.2010 um 22:04 schrieb Avi Kivity :
On 03/25/2010 06:54 PM, Dale Farnsworth wrote:
I'm beginning to look at implementing KVM on MIPS. I've tried to
search
for any work-in-progress on this but haven't found much at all.
Google comes up with some hits, but nothing concrete.
If yo
On 03/25/2010 08:17 PM, Cam Macdonell wrote:
I had a hunch it was probably considered. That explains why irqfd
doesn't have a datamatch field. I guess supporting multiple MSI
vectors with one doorbell per guest isn't possible if one 1 bit of
information can be communicated.
Actually
On 03/25/2010 06:54 PM, Dale Farnsworth wrote:
I'm beginning to look at implementing KVM on MIPS. I've tried to search
for any work-in-progress on this but haven't found much at all.
Google comes up with some hits, but nothing concrete.
If you know of anyone who is working on this or of
On 03/25/2010 10:23 PM, Pekka Enberg wrote:
Hi Avi,
Avi Kivity wrote:
When you come up against something that is undocumented or badly
described, please complain on k...@. We will then update the
documentation.
So one thing I'm wondering is in what mode do we enter the guest? Is
that entir
Hi Avi,
Avi Kivity wrote:
When you come up against something that is undocumented or badly
described, please complain on k...@. We will then update the documentation.
So one thing I'm wondering is in what mode do we enter the guest? Is
that entirely specified with KVM_SET_REGS and KVM_SET_SR
On Thu, Mar 25, 2010 at 11:48 AM, Avi Kivity wrote:
> On 03/25/2010 07:35 PM, Cam Macdonell wrote:
>>
>>> Ah, I see. You adjusted for the different behaviours in the driver.
>>>
>>> Still I recommend dropping the status register: this allows single-msi
>>> and
>>> PIRQ to behave the same way. Al
On Thu, Mar 25, 2010 at 06:25:56PM +0200, Avi Kivity wrote:
> On 03/24/2010 11:24 PM, Marcelo Tosatti wrote:
> >Which allows code to execute on remote cpus while receiving interrupts.
> >
> >Also move late smp initialization to common code, and the smp loop
> >to C code.
>
>
> >+
> >+void smp_loo
* Hannes Reinecke (h...@suse.de) wrote:
> Hi all,
>
> I'm trying to setup a system with device-passthrough for
> an ixgbe NIC.
> The device itself seems to work, but it isn't using MSI-X.
> So some more advanced features like DCB offloading etc
> won't work.
Please send the relevant dmesg from th
On 03/25/2010 07:35 PM, Cam Macdonell wrote:
Ah, I see. You adjusted for the different behaviours in the driver.
Still I recommend dropping the status register: this allows single-msi and
PIRQ to behave the same way. Also it is racy, if two guests signal a third,
they will overwrite each oth
On Thu, Mar 25, 2010 at 11:02 AM, Avi Kivity wrote:
> On 03/25/2010 06:50 PM, Cam Macdonell wrote:
>>
>>> Please put the spec somewhere publicly accessible with a permanent URL.
>>> I
>>> suggest a new qemu.git directory specs/. It's more important than the
>>> code
>>> IMO.
>>>
>>
>> Sorry to b
I'm beginning to look at implementing KVM on MIPS. I've tried to search
for any work-in-progress on this but haven't found much at all.
If you know of anyone who is working on this or of pitfalls I should
consider before jumping in, please let me know.
Thanks,
-Dale
--
To unsubscribe from this l
On Thu, Mar 25, 2010 at 10:34 AM, Michael S. Tsirkin wrote:
> On Thu, Mar 25, 2010 at 10:30:42AM -0600, Cam Macdonell wrote:
>> On Thu, Mar 25, 2010 at 3:05 AM, Michael S. Tsirkin wrote:
>> > On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
>> >> This patch adds a driver for my shar
On 03/25/2010 06:50 PM, Cam Macdonell wrote:
Please put the spec somewhere publicly accessible with a permanent URL. I
suggest a new qemu.git directory specs/. It's more important than the code
IMO.
Sorry to be pedantic, do you want a URL or the spec as part of a patch
that adds it as
On 03/25/2010 06:37 PM, Michael S. Tsirkin wrote:
On Thu, Mar 25, 2010 at 06:36:02PM +0200, Avi Kivity wrote:
On 03/25/2010 11:05 AM, Michael S. Tsirkin wrote:
+static struct pci_device_id ivshmem_pci_ids[] __devinitdata = {
+{
+.vendor =0x1af4,
+.devic
On 03/25/2010 06:40 PM, Michael S. Tsirkin wrote:
On Thu, Mar 25, 2010 at 06:32:15PM +0200, Avi Kivity wrote:
On 03/25/2010 06:23 PM, Anthony Liguori wrote:
There has been previous discussion of virtio, however while virtio is
good for exporting guest memory, it's not ideal for import
On Thu, Mar 25, 2010 at 3:04 AM, Avi Kivity wrote:
> On 03/25/2010 08:08 AM, Cam Macdonell wrote:
>>
>> Support an inter-vm shared memory device that maps a shared-memory object
>> as a PCI device in the guest. This patch also supports interrupts between
>> guest by communicating over a unix doma
On Thu, Mar 25, 2010 at 10:24:20AM -0600, Cam Macdonell wrote:
> On Thu, Mar 25, 2010 at 3:46 AM, Avi Kivity wrote:
> > On 03/25/2010 08:09 AM, Cam Macdonell wrote:
> >>
> >> This patch adds a driver for my shared memory PCI device using the uio_pci
> >> interface. The driver has three memory reg
On Thu, Mar 25, 2010 at 06:32:15PM +0200, Avi Kivity wrote:
> On 03/25/2010 06:23 PM, Anthony Liguori wrote:
>>> There has been previous discussion of virtio, however while virtio is
>>> good for exporting guest memory, it's not ideal for importing memory
>>> into a guest.
>>
>> virtio is a DMA-bas
On Thu, Mar 25, 2010 at 06:36:02PM +0200, Avi Kivity wrote:
> On 03/25/2010 11:05 AM, Michael S. Tsirkin wrote:
>>
>>> +static struct pci_device_id ivshmem_pci_ids[] __devinitdata = {
>>> +{
>>> +.vendor =0x1af4,
>>> +.device =0x1110,
>>>
>> vendor ids must be regi
On Thu, Mar 25, 2010 at 10:30:42AM -0600, Cam Macdonell wrote:
> On Thu, Mar 25, 2010 at 3:05 AM, Michael S. Tsirkin wrote:
> > On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
> >> This patch adds a driver for my shared memory PCI device using the uio_pci
> >> interface. The driver
On Thu, Mar 25, 2010 at 11:23:05AM -0500, Anthony Liguori wrote:
> On 03/25/2010 11:18 AM, Cam Macdonell wrote:
>> On Thu, Mar 25, 2010 at 3:15 AM, Michael S. Tsirkin wrote:
>>
>>> On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
>>>
This patch adds a driver for my sha
On 03/25/2010 11:05 AM, Michael S. Tsirkin wrote:
+static struct pci_device_id ivshmem_pci_ids[] __devinitdata = {
+{
+.vendor =0x1af4,
+.device =0x1110,
vendor ids must be registered with PCI SIG.
this one does not seem to be registered.
That's the Qumr
On 03/25/2010 06:24 PM, Cam Macdonell wrote:
There is now a generic PCI 2.3 driver that can handle all PCI devices. It
doesn't support MSI, but if we add MSI support then it can be used without
the need for a specialized driver.
Agreed, I'd be happy to use the generic driver if MSI is t
On 03/25/2010 06:23 PM, Anthony Liguori wrote:
There has been previous discussion of virtio, however while virtio is
good for exporting guest memory, it's not ideal for importing memory
into a guest.
virtio is a DMA-based API which means that it doesn't assume cache
coherent shared memory. Th
On Thu, Mar 25, 2010 at 3:05 AM, Michael S. Tsirkin wrote:
> On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
>> This patch adds a driver for my shared memory PCI device using the uio_pci
>> interface. The driver has three memory regions. The first memory region is
>> for
>> devic
On 03/24/2010 11:24 PM, Marcelo Tosatti wrote:
Signed-off-by: Marcelo Tosatti
Whoa, memory hotplug.
--
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 m
On 03/24/2010 11:24 PM, Marcelo Tosatti wrote:
Which allows code to execute on remote cpus while receiving interrupts.
Also move late smp initialization to common code, and the smp loop
to C code.
+
+void smp_loop(void)
+{
+void (*fn)(void *data);
+void *data;
+
+asm volatile
On Thu, Mar 25, 2010 at 3:46 AM, Avi Kivity wrote:
> On 03/25/2010 08:09 AM, Cam Macdonell wrote:
>>
>> This patch adds a driver for my shared memory PCI device using the uio_pci
>> interface. The driver has three memory regions. The first memory region
>> is for
>> device registers for sending
On 03/25/2010 11:18 AM, Cam Macdonell wrote:
On Thu, Mar 25, 2010 at 3:15 AM, Michael S. Tsirkin wrote:
On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
This patch adds a driver for my shared memory PCI device using the uio_pci
interface. The driver has three memory re
On 03/24/2010 04:21 PM, Alexander Graf wrote:
The same code works with qemu-kvm.git. Cherry picking this commit
(51c0dad5ce383be94ca7c46e491ada17cc9ec416) also makes it work in
0.12-stable.
Thus I'd incline we also take this patch into 0.12-stable.
Done.
--
error compiling committee.c:
On Thu, Mar 25, 2010 at 3:15 AM, Michael S. Tsirkin wrote:
> On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
>> This patch adds a driver for my shared memory PCI device using the uio_pci
>> interface. The driver has three memory regions. The first memory region is
>> for
>> devic
On Thu, Mar 25, 2010 at 3:21 AM, Michael S. Tsirkin wrote:
> On Thu, Mar 25, 2010 at 11:04:54AM +0200, Avi Kivity wrote:
>> Again, I recommend Rusty's virtio-pci for inspiration.
>
> Not just inspiration, how about building on virtio-pci?
Virtio was discussed at good length last year on a previou
On Wed, Mar 24, 2010 at 01:22:37PM -0700, Badari Pulavarty wrote:
> Yes. This is with default (writeback) cache model. As mentioned earlier,
> readhead is helping here
> and most cases, data would be ready in the pagecache.
Ok. cache=writeback performance is something I haven't bothered looking
On 03/25/2010 05:48 PM, Christoph Hellwig wrote:
On Thu, Mar 25, 2010 at 08:29:03AM +0200, Avi Kivity wrote:
We still have a virtio implementation in userspace for file-based images.
In any case, the file APIs are not asynchronous so we'll need a thread
pool. That will probably minimize th
On Thu, Mar 25, 2010 at 08:29:03AM +0200, Avi Kivity wrote:
> We still have a virtio implementation in userspace for file-based images.
>
> In any case, the file APIs are not asynchronous so we'll need a thread
> pool. That will probably minimize the difference in performance between
> the use
Sheng Yang wrote:
> On Wednesday 24 March 2010 23:54:15 Hannes Reinecke wrote:
>> Hi all,
>>
>> I'm trying to setup a system with device-passthrough for
>> an ixgbe NIC.
>> The device itself seems to work, but it isn't using MSI-X.
>> So some more advanced features like DCB offloading etc
>> won't
Log emulated instructions in ftrace, especially if they failed.
Signed-off-by: Avi Kivity
---
arch/x86/kvm/trace.h | 86 ++
arch/x86/kvm/x86.c |4 ++
2 files changed, 90 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/trace.h b/arc
Currently if we an instruction spans a page boundary, when we fetch the
second half we overwrite the first half. This prevents us from tracing
the full instruction opcodes.
Fix by appending the second half to the first.
Signed-off-by: Avi Kivity
---
arch/x86/kvm/emulate.c | 19 ++
Add a trace of instruction emulation into ftrace. This can help analyze
performance issues, or, in the case of failed emulation, identify the
missing instructions.
Avi Kivity (2):
KVM: x86 emulator: Don't overwrite decode cache
KVM: Trace emulated instructions
arch/x86/kvm/emulate.c | 19
Avi Kivity wrote:
For the case where the file is actually a partition, use
submit_bio(). When the file is a file, keep it in qemu, that path is
going to be slower anyway.
[CUT]
Christoph Hellwig wrote:
On Tue, Mar 23, 2010 at 12:03:14PM +0200, Avi Kivity wrote:
I also think it should be
Avi Kivity wrote:
On 03/24/2010 10:22 PM, Badari Pulavarty wrote:
Which caching mode is this? I assume data=writeback, because otherwise
you'd be doing synchronous I/O directly from the handler.
Yes. This is with default (writeback) cache model. As mentioned
earlier, readhead is helping her
Em Thu, Mar 25, 2010 at 04:47:44PM +0800, Zhang, Yanmin escreveu:
> On Thu, 2010-03-25 at 16:02 +0800, Li Zefan wrote:
> Thanks for reporting it. Arnaldo, could you pick up below patch?
> Zefan, Could you try it?
Sure thing, will stash them in today's push to Ingo, thanks!
- Arnaldo
--
To unsubsc
Windows guests will display a dialog for the user and
refuse to shutdown when the system_powerdown command
is sent. Let's just remove this test from the windows
set of tests.
Signed-off-by: Lucas Meneghel Rodrigues
---
client/tests/kvm/tests_base.cfg.sample |2 +-
1 files changed, 1 insertio
On 03/24/2010 06:46 PM, Andre Przywara wrote:
There is a quirk for AMD K8 CPUs in many Linux kernels (see
arch/x86/kernel/cpu/mcheck/mce.c:__mcheck_cpu_apply_quirks()) that
clears bit 10 in that MCE related MSR. KVM can only cope with all
zeros or all ones, so it will inject a #GP into the guest,
On 03/25/2010 02:00 PM, Pekka Enberg wrote:
I don't think such a technical description of an implementation
detail has a place in the API reference; maybe in internal
documentation.
Sure but it would be nice to have something along the lines of "This
is needed on Intel hardware because of a
Avi Kivity kirjoitti:
On 03/25/2010 12:36 PM, Pekka Enberg wrote:
+4.35 KVM_SET_TSS_ADDR
+
+Capability: KVM_CAP_SET_TSS_ADDR
+Architectures: x86
+Type: vm ioctl
+Parameters: unsigned long tss_address (in)
+Returns: 0 on success, -1 on error
+
+This ioctl defines the physical address of a three-p
On 03/25/2010 01:54 PM, Alexander Graf wrote:
Am 25.03.2010 um 12:49 schrieb Avi Kivity :
On 03/25/2010 01:10 PM, Alexander Graf wrote:
Am 25.03.2010 um 11:31 schrieb Avi Kivity :
+It is recommended to use this API instead of the
KVM_SET_MEMORY_REGION ioctl.
Why? What's wrong with SET_
On 03/24/2010 05:35 PM, Michael Tokarev wrote:
At least having a way to accept complete acpi table (with header
and checksum and everything) is - IMHO - a good thing.
Agreed.
But I'm not sure about the OEM ID strings in other tables in seabios, --
it is quite ugly, both in implementation
Am 25.03.2010 um 12:49 schrieb Avi Kivity :
On 03/25/2010 01:10 PM, Alexander Graf wrote:
Am 25.03.2010 um 11:31 schrieb Avi Kivity :
+It is recommended to use this API instead of the
KVM_SET_MEMORY_REGION ioctl.
Why? What's wrong with SET_MEM_REGION?
It doesn't allow any control ov
On 03/25/2010 01:10 PM, Alexander Graf wrote:
Am 25.03.2010 um 11:31 schrieb Avi Kivity :
+It is recommended to use this API instead of the
KVM_SET_MEMORY_REGION ioctl.
Why? What's wrong with SET_MEM_REGION?
It doesn't allow any control over the memory. So it found its way into
Docume
Am 25.03.2010 um 11:31 schrieb Avi Kivity :
+It is recommended to use this API instead of the
KVM_SET_MEMORY_REGION ioctl.
Why? What's wrong with SET_MEM_REGION?
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
On 03/25/2010 12:36 PM, Pekka Enberg wrote:
+4.35 KVM_SET_TSS_ADDR
+
+Capability: KVM_CAP_SET_TSS_ADDR
+Architectures: x86
+Type: vm ioctl
+Parameters: unsigned long tss_address (in)
+Returns: 0 on success, -1 on error
+
+This ioctl defines the physical address of a three-page region in
the gues
Hi Avi,
Avi Kivity kirjoitti:
Signed-off-by: Avi Kivity
---
Documentation/kvm/api.txt | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index 22af28a..8f45099 100644
--- a/Documentation/kvm/api.txt
+++
Avi Kivity kirjoitti:
Signed-off-by: Avi Kivity
Acked-by: Pekka Enberg
---
Documentation/kvm/api.txt | 43 +++
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index d170cb4..22af
Avi Kivity (2):
KVM: Document KVM_SET_USER_MEMORY_REGION
KVM: Document KVM_SET_TSS_ADDR
Documentation/kvm/api.txt | 59 +
1 files changed, 59 insertions(+), 0 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the b
Signed-off-by: Avi Kivity
---
Documentation/kvm/api.txt | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index 22af28a..8f45099 100644
--- a/Documentation/kvm/api.txt
+++ b/Documentation/kvm/api.txt
@@ -
Signed-off-by: Avi Kivity
---
Documentation/kvm/api.txt | 43 +++
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index d170cb4..22af28a 100644
--- a/Documentation/kvm/api.txt
+++ b/Doc
On Thu, Mar 25, 2010 at 11:58:30AM +0200, Avi Kivity wrote:
> On 03/25/2010 11:44 AM, Michael S. Tsirkin wrote:
>> On Thu, Mar 25, 2010 at 11:40:09AM +0200, Avi Kivity wrote:
>>
>>> On 03/25/2010 11:15 AM, Michael S. Tsirkin wrote:
>>>
- Why are you using 32 bit long memory accesses
On 03/25/2010 11:44 AM, Michael S. Tsirkin wrote:
On Thu, Mar 25, 2010 at 11:40:09AM +0200, Avi Kivity wrote:
On 03/25/2010 11:15 AM, Michael S. Tsirkin wrote:
- Why are you using 32 bit long memory accesses for interrupts?
16 bit IO eould be enough and it's faster. This what virt
On Thu, Mar 25, 2010 at 11:40:09AM +0200, Avi Kivity wrote:
> On 03/25/2010 11:15 AM, Michael S. Tsirkin wrote:
>>
>> - Why are you using 32 bit long memory accesses for interrupts?
>>16 bit IO eould be enough and it's faster. This what virtio-pci does.
>>
>>
>
> Why is 16 bit io faster?
S
On 03/25/2010 11:05 AM, Michael S. Tsirkin wrote:
coding style rule violation
Plus it uses spaces instead of tabs for indents.
--
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.
On 03/25/2010 08:09 AM, Cam Macdonell wrote:
This patch adds a driver for my shared memory PCI device using the uio_pci
interface. The driver has three memory regions. The first memory region is for
device registers for sending interrupts. The second BAR is for receiving MSI-X
interrupts and th
On 03/25/10 10:39, Jan Kiszka wrote:
Zhang, Xiantao wrote:
For ia64 part, maybe we can keep the current qemu-kvm.git for the users. And it
is not a must to push it into Qemu upstream.
Xiantao
Does it still build& work? Does someone test it at least infrequently?
Or are there users?
There w
On 03/25/2010 11:15 AM, Michael S. Tsirkin wrote:
- Why are you using 32 bit long memory accesses for interrupts?
16 bit IO eould be enough and it's faster. This what virtio-pci does.
Why is 16 bit io faster?
--
error compiling committee.c: too many arguments to function
--
To unsubs
Zhang, Xiantao wrote:
> Jes Sorensen wrote:
>> On 03/23/10 13:45, Anthony Liguori wrote:
>>> I don't think we can pull in:
>>>
>>> - extboot
>>> - ia64
>>> - in-kernel pit[1]
>>> - associated command line options
>>> - device passthrough
>>>
>>> The question is, if we dropped those things, would pe
On 03/25/2010 11:26 AM, Markus Armbruster wrote:
Avi Kivity writes:
Please put the spec somewhere publicly accessible with a permanent
URL. I suggest a new qemu.git directory specs/. It's more important
than the code IMO.
What about docs/? It already exists.
docs/ would be
On Sat, Mar 20, 2010 at 09:49:46AM +0200, Avi Kivity wrote:
> On 03/19/2010 11:17 AM, Sebastian Hetze wrote:
>> On Fri, Mar 19, 2010 at 10:37:00AM +0200, Avi Kivity wrote:
>>
>>> On 03/19/2010 09:30 AM, Sebastian Hetze wrote:
>>>
Hi *,
in the dmesg/kern.log of my ubuntu 2.6
Avi Kivity writes:
> Please put the spec somewhere publicly accessible with a permanent
> URL. I suggest a new qemu.git directory specs/. It's more important
> than the code IMO.
What about docs/? It already exists.
[...]
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
t
On Thu, Mar 25, 2010 at 11:04:54AM +0200, Avi Kivity wrote:
> Again, I recommend Rusty's virtio-pci for inspiration.
Not just inspiration, how about building on virtio-pci?
--
MST
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.
On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
> This patch adds a driver for my shared memory PCI device using the uio_pci
> interface. The driver has three memory regions. The first memory region is
> for
> device registers for sending interrupts. The second BAR is for receivin
On Thu, Mar 25, 2010 at 12:09:36AM -0600, Cam Macdonell wrote:
> This patch adds a driver for my shared memory PCI device using the uio_pci
> interface. The driver has three memory regions. The first memory region is
> for
> device registers for sending interrupts. The second BAR is for receivin
On 03/25/2010 08:08 AM, Cam Macdonell wrote:
Support an inter-vm shared memory device that maps a shared-memory object
as a PCI device in the guest. This patch also supports interrupts between
guest by communicating over a unix domain socket. This patch applies to the
qemu-kvm repository.
Chan
On Wed, 2010-03-24 at 20:20 +0200, Avi Kivity wrote:
> On 03/24/2010 07:47 PM, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Mar 24, 2010 at 06:09:30PM +0200, Avi Kivity escreveu:
> >
> >> Doesn't perf already has a dependency on naming conventions for finding
> >> debug information?
> >>
>
>>> Parameter --pid (or -p) of perf currently means a thread-wide collection.
>>> For exmaple, if a process whose id is has 10 threads, 'perf top -p
>>> '
>>> just collects the main thread statistics. That's misleading. Users are
>>> used to attach a whole process when debugging a process
On Thu, 2010-03-25 at 16:02 +0800, Li Zefan wrote:
> Zhang, Yanmin wrote:
> > From: Zhang, Yanmin
> >
> > Parameter --pid (or -p) of perf currently means a thread-wide collection.
> > For exmaple, if a process whose id is has 10 threads, 'perf top -p
> > '
> > just collects the main thr
Zhang, Yanmin wrote:
> From: Zhang, Yanmin
>
> Parameter --pid (or -p) of perf currently means a thread-wide collection.
> For exmaple, if a process whose id is has 10 threads, 'perf top -p '
> just collects the main thread statistics. That's misleading. Users are
> used to attach a whol
On 03/24/2010 10:22 PM, Badari Pulavarty wrote:
Which caching mode is this? I assume data=writeback, because otherwise
you'd be doing synchronous I/O directly from the handler.
Yes. This is with default (writeback) cache model. As mentioned
earlier, readhead is helping here
and most cases,
84 matches
Mail list logo
