Hello,
I have found an issue for compiling on 32 Bit machines in
v2.6.22-rc1-g1ab29f3.
I'm not sure if I have set the #ifdef CONFIG_X86_64 at the right place.
Please have a look at it. With this patch v2.6.22-rc1-g1ab29f3 compiles
und runs fine.
Daniel
Signed-off-by: Daniel Hecken [EMAIL
Hi,
I saw some discussions on the topic but no progress. I did an
experiment to make guest page be allocated dynamically and swap out.
please see attachment patches. It's not yet for merge but I'd like get
some suggestions and help. Patches (against kvm-19) work here but
maybe not very stable as
Daniel Hecken wrote:
Hello,
I have found an issue for compiling on 32 Bit machines in
v2.6.22-rc1-g1ab29f3.
I'm not sure if I have set the #ifdef CONFIG_X86_64 at the right place.
Please have a look at it. With this patch v2.6.22-rc1-g1ab29f3 compiles
und runs fine.
Hi,
I saw some discussions on the topic but no progress. I did an
experiment to make guest page be allocated dynamically and swap out.
Wow, that's a very nice/welcomed/hard experience.
please see attachment patches. It's not yet for merge but I'd like get
some suggestions and help. Patches
This is quite easy with KVM. I like the approach that vmchannel has
taken. A simple PCI device. That gives you a discovery mechanism for
shared memory and an interrupt and then you can just implement a ring
queue using those mechanisms (along with a PIO port for signaling from
the
Avi Kivity schrieb:
Daniel Hecken wrote:
Hello,
I have found an issue for compiling on 32 Bit machines in
v2.6.22-rc1-g1ab29f3.
I'm not sure if I have set the #ifdef CONFIG_X86_64 at the right place.
Please have a look at it. With this patch v2.6.22-rc1-g1ab29f3 compiles
und runs fine.
Shaohua Li wrote:
+EXPORT_SYMBOL(delete_from_swap_cache);
+EXPORT_SYMBOL(move_to_swap_cache);
+EXPORT_SYMBOL(lookup_swap_cache);
+EXPORT_SYMBOL(read_swap_cache_async);
+EXPORT_SYMBOL(get_swap_page);
+EXPORT_SYMBOL(swap_free);
+EXPORT_SYMBOL(add_to_page_cache_lru);
Use EXPORT_SYMBOL_GPL for
Shaohua Li wrote:
Hi,
I saw some discussions on the topic but no progress. I did an
experiment to make guest page be allocated dynamically and swap out.
please see attachment patches. It's not yet for merge but I'd like get
some suggestions and help. Patches (against kvm-19) work here but
On Mon, May 21, 2007 at 11:17:06AM +0200, Carsten Otte wrote:
Shaohua Li wrote:
+EXPORT_SYMBOL(delete_from_swap_cache);
+EXPORT_SYMBOL(move_to_swap_cache);
+EXPORT_SYMBOL(lookup_swap_cache);
+EXPORT_SYMBOL(read_swap_cache_async);
+EXPORT_SYMBOL(get_swap_page);
On Mon, 21 May 2007 13:28:03 +0200,
Arnd Bergmann [EMAIL PROTECTED] wrote:
We've had the same discussion about PCI as virtual device abstraction
recently when hpa made the suggestions to get a set of PCI device
numbers registered for Linux.
(If you want to read it up, it's the thread at
Avi Kivity wrote:
For one thing, kvm uses page-private to store its rmap information.
This is lost if regular mappings are used.
More importantly, both the regular address space and kvm will want to be
called when a page is paged out, while this is doable, it isn't easy.
Taking the long
Carsten Otte wrote:
Avi Kivity wrote:
For one thing, kvm uses page-private to store its rmap information.
This is lost if regular mappings are used.
More importantly, both the regular address space and kvm will want to
be called when a page is paged out, while this is doable, it isn't
On Monday 21 May 2007, Cornelia Huck wrote:
IRQ numbers are evil :)
yes, but getting rid of them is an entirely different discussion.
I really think that in the first step, you should be able to
use its external interrupts with the same request_irq interface
as the other architectures.
Avi Kivity wrote:
The pte is stored/cached in two different places (in addition to what
Linux already knows about):
- in the shadow page tables
- in the tlbs of the vcpus that may have referenced the page
so, when swapping out the page, you need to use the kvm rmap to find all
shadow
Carsten Otte wrote:
An example: suppose host pfn 7 is allocated as guest pfn 8 (and
therefore, userspace address 0x8000). Suppose further the guest maps
guest pfn 8 to guest virtual 0x1 and guest virtal 0x11000.
Aren't there three tlbs you need to shoot down? host virtual
David Abrahams wrote:
When I have windows XP running under kvm, I get
[EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
aplay: main:550: audio open error: Device or resource busy
As soon as I shut down
Carsten Otte wrote:
Avi Kivity wrote:
Interesting. And if you have multiple guest virtual to guest
physical translations, the hardware knows to flush them when the host
virtual to host physical entry is flushed?
Yes, the cpu flushes all of them.
Ooh, I want one too.
--
error compiling
You have to make QEMU use ALSA as your sound system and specify a mixer
device for input and output. This can be done using some environment
variables that should be set before the qemu binary is run.
The following may work:
export QEMU_AUDIO_DRV=alsa # the default is OSS if I recall
Avi Kivity wrote:
Interesting. And if you have multiple guest virtual to guest physical
translations, the hardware knows to flush them when the host virtual to
host physical entry is flushed?
Yes, the cpu flushes all of them.
so long,
Carsten
Arnd Bergmann wrote:
On Monday 21 May 2007, Christian Borntraeger wrote:
This is quite easy with KVM. I like the approach that vmchannel has
taken. A simple PCI device. That gives you a discovery mechanism for
shared memory and an interrupt and then you can just implement a ring
On Mon, May 21, 2007 at 08:37:48AM -0700, Shahar Frank wrote:
You have to make QEMU use ALSA as your sound system and specify a
mixer device for input and output. This can be done using some
environment variables that should be set before the qemu binary is
run.
From the ALSA wiki:
For
OK, so what are we doing here? We're using a PCI abstraction, as a
common abstraction,which is not common really, because we don't have a
common abstraction? So we describe all these non-pci resources with a
pci abstraction?
I don't get it at all. I really think the resource interface idea I
On 5/21/07, Anthony Liguori [EMAIL PROTECTED] wrote:
ron minnich wrote:
OK, so what are we doing here? We're using a PCI abstraction, as a
common abstraction,which is not common really, because we don't have a
common abstraction? So we describe all these non-pci resources with a
pci
ron minnich wrote:
On 5/21/07, Anthony Liguori [EMAIL PROTECTED] wrote:
No. You're confusing PV device discovery with the actual paravirtual
transport. In a fully virtual environment like KVM, a PCI bus is
present. You need some way for the guest to detect that a PV device is
present. The
Eric Van Hensbergen wrote:
On 5/21/07, Anthony Liguori [EMAIL PROTECTED] wrote:
ron minnich wrote:
OK, so what are we doing here? We're using a PCI abstraction, as a
common abstraction,which is not common really, because we don't have a
common abstraction? So we describe all these non-pci
25 matches
Mail list logo
