Hello! A first-time poster (and user) is here... but not a newbie ;)
Some time ago I tried KVM for the first time, on an AMD X2-64 system
(BE-2400 processor, also tried with other similar processors, like
"plain" X2-64 4888+ etc), first with 2.6.23 vanilla kernel compiled
for 64 bits, SMP. After
Am Freitag, 1. Februar 2008 schrieb Christian Borntraeger:
> Right. I will fix that with an additional patch.
This patch goes on top of the minor number patch. Please let me know if
you want a merged patch:
Currently virtio_blk creates the disk name combinging "vd" with 'a'++.
This will give str
Hello Michael,
On Friday 01 February 2008 13:30:03 Michael Tokarev wrote:
> Hello! A first-time poster (and user) is here... but not a newbie ;)
>
> Some time ago I tried KVM for the first time, on an AMD X2-64 system
> (BE-2400 processor, also tried with other similar processors, like
> "plain"
Hi, Avi
Here is the patchset which enabling EPT for VMX. We tested it with 32e host,
and it works well on Linux, Windows, also SMP with kernel build, though the X
Window and windows need a patch for qemu to solve the dirty bitmap problem.
The format of EPT entry is different from the page tabl
From 51705fa4cee9ee6eb4244599a4eb26bb055199c9 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 05:08:35 +0800
Subject: [PATCH] KVM: Add EPT support in kvm_arch
EPT pointer is a per-domain data, and it contains info more than root_hpa. It
may can be put in a bette
From 22895ad4778189242dd546c98709bcd3fadb0cf6 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 06:32:19 +0800
Subject: [PATCH] KVM: MMU: Add Two Level Paging (TLP)
For EPT's path is very different from NPT's, the return value of the function
tlp_enable() indicate
From 5062793a4aae25b8f701decbcf6dead9a4a38348 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 06:51:01 +0800
Subject: [PATCH] KVM: VMX: Enable EPT feature
For EPT's entry format is different from page table, we would set up EPT in
this
patch. In EPT, hardware C
From 720eee463536fdb6e15dcc5388754ea229c71118 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 06:53:39 +0800
Subject: [PATCH] KVM: VMX: Add swap support for EPT
Add tlp_unmap() in kvm_x86_ops, to support swap of EPT pages. Now EPT can
support linux swap along wi
From 1b7e6dcffe5845a05b7bfe42b52d680f17f34d5d Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 06:41:35 +0800
Subject: [PATCH] KVM: Export necessary function to modules()
The function load_pdptrs() is needed by VMX for EPT in PAE mode. The function
gfn_to_hva() i
From e5ed046f6862a9e314f334458d46f871b7fb8b58 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 06:32:17 +0800
Subject: [PATCH] KVM: Common interface of TLP and feature detection for EPT
The patch export tlp_enabled() from kvm_x86_ops as common interface, and
make
From de2bedf0890c95828b07ba3d2d98025fd39050a1 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 07:33:13 +0800
Subject: [PATCH] kvm: qemu: Enable EPT support for real mode
The patch allocated one page from 0xcf000 (the last page of vga bios region),
took it as the
Amit Shah wrote:
> On Friday 01 February 2008 13:30:03 Michael Tokarev wrote:
>> Some time ago I tried KVM for the first time, on an AMD X2-64 system
>> (BE-2400 processor, also tried with other similar processors, like
>> "plain" X2-64 4888+ etc), first with 2.6.23 vanilla kernel compiled
>> for
I will be offline for the entire week of Feb 2 - Feb 9. I will only be
reachable by specially trained St. Bernards.
Andrew, if kvm.git gives you undue trouble, please drop it and I'll sort
out the mess when I return.
--
Any sufficiently difficult bug is indistinguishable from a feature.
---
Yang, Sheng wrote:
> Hi, Avi
>
> Here is the patchset which enabling EPT for VMX. We tested it with 32e host,
> and it works well on Linux, Windows, also SMP with kernel build, though the X
> Window and windows need a patch for qemu to solve the dirty bitmap problem.
>
> The format of EPT entry
From: Xiantao Zhang <[EMAIL PROTECTED]>
Date: Fri, 1 Feb 2008 17:18:03 +0800
Subject: [PATCH] Make non-x86 arch partially support make sync.
Make non-x86 arch partially support make sync, and other archs
can get right header files for userspace.
Signed-off-by: Xiantao Zhang <[EMAIL PROTECTED]>
---
Anthony Liguori wrote:
> KVM supports more than 2GB of memory for x86_64 hosts. The following patch
> fixes a number of type related issues where int's were being used when they
> shouldn't have been. It also introduces CMOS support so the BIOS can build
> the appropriate e820 tables.
> [...]
>
Anthony Liguori wrote:
> This patch actually enables KVM support for QEMU. I apologize that it is so
> large but this was the only sane way to preserve bisectability.
>
> The goal of this patch is to add KVM support, but not to impact users when
> KVM isn't being used. It achieves this by using
do_wp_page can reach the _end callout without passing the _begin
callout. This prevents making the _end unles the _begin has also
been made.
Index: mmu_notifiers-cl-v5/mm/memory.c
===
--- mmu_notifiers-cl-v5.orig/mm/memory.c2
On Fri, Feb 01, 2008 at 04:32:21AM -0600, Robin Holt wrote:
> On Thu, Jan 31, 2008 at 08:43:58PM -0800, Christoph Lameter wrote:
> > On Thu, 31 Jan 2008, Robin Holt wrote:
> >
> > > > Index: linux-2.6/mm/memory.c
> > > ...
> > > > @@ -1668,6 +1678,7 @@ gotten:
> > > > page_cache_re
On Thu, Jan 31, 2008 at 08:43:58PM -0800, Christoph Lameter wrote:
> On Thu, 31 Jan 2008, Robin Holt wrote:
>
> > > Index: linux-2.6/mm/memory.c
> > ...
> > > @@ -1668,6 +1678,7 @@ gotten:
> > > page_cache_release(old_page);
> > > unlock:
> > > pte_unmap_unlock(page_table, ptl);
> > >
OK. Now that release has been moved, I think I agree with you that the
down_write(mmap_sem) can be used as our lock again and still work for
Jack. I would like a ruling from Jack as well.
Thanks,
Robin
-
This SF.net email i
On Fri, Feb 01, 2008 at 04:55:16AM -0600, Robin Holt wrote:
> OK. Now that release has been moved, I think I agree with you that the
> down_write(mmap_sem) can be used as our lock again and still work for
> Jack. I would like a ruling from Jack as well.
Ignore this, I was in the wrong work area.
With this set of patches, I think we have enough to get xpmem working
with most types of mappings. In the past, we operated without any of
these callouts by significantly restricting why types of mappings could
remotely fault and what types of operations the user could do. With
this set, I am ce
On Thu, Jan 31, 2008 at 05:37:21PM -0800, Christoph Lameter wrote:
> On Fri, 1 Feb 2008, Andrea Arcangeli wrote:
>
> > I appreciate the review! I hope my entirely bug free and
> > strightforward #v5 will strongly increase the probability of getting
> > this in sooner than later. If something else
On Thu, Jan 31, 2008 at 05:44:24PM -0800, Christoph Lameter wrote:
> The trouble is that the invalidates are much more expensive if you have to
> send theses to remote partitions (XPmem). And its really great if you can
> simple tear down everything. Certainly this is a significant improvement
>
Argh,
Here is the correct one. Sorry
On Fri, Feb 01, 2008 at 05:58:41AM -0600, Robin Holt wrote:
> With this set of patches, I think we have enough to get xpmem working
> with most types of mappings. In the past, we operated without any of
> these callouts by significantly restricting why types
Fabrice Bellard wrote:
> Some questions:
>
> - QEMU already maintains modified page status for VGA memory (and
> kqemu for example fully supports that), so I don't see why KVM needs a
> new method.
KQEMU passes the dirty bitmap directly to the kernel. KVM does
aggressive shadow page table cach
Anthony Liguori wrote:
> Fabrice Bellard wrote:
>> Anthony Liguori wrote:
>>> +/* above 4giga memory allocation */
>>> +if (above_4g_mem_size > 0) {
>>> +ram_addr = qemu_ram_alloc(above_4g_mem_size);
>>> +cpu_register_physical_memory(0x1,
>>> above_4g_mem_size, ram_
Bugs item #188, was opened at 2008-02-01 15:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=188&group_id=180599
Please note that this message will contain a full copy
Fabrice Bellard wrote:
> Anthony Liguori wrote:
>> +/* above 4giga memory allocation */
>> +if (above_4g_mem_size > 0) {
>> +ram_addr = qemu_ram_alloc(above_4g_mem_size);
>> +cpu_register_physical_memory(0x1, above_4g_mem_size,
>> ram_addr);
>> +}
>> +
>
> Why d
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> I think I'll change this too into a single qemu_ram_alloc. That will
>> fix the bug with KVM when using -kernel and large memory anyway :-)
>>
>
> Won't that cause all of the memory in the hole to be wasted?
>
> You could munmap() it, but it
Paul Brook wrote:
>>> I agree with the fact that ram_size should be 64 bit. Maybe each
>>> machine could test the value and emit an error message if it is too
>>> big. Maybe an uint64_t would be better though.
>> uint64_t is probably more reasonable. I wouldn't begin to know what the
>> appropriat
> > I agree with the fact that ram_size should be 64 bit. Maybe each
> > machine could test the value and emit an error message if it is too
> > big. Maybe an uint64_t would be better though.
>
> uint64_t is probably more reasonable. I wouldn't begin to know what the
> appropriate amount of ram wa
Anthony Liguori writes ("[Qemu-devel] Re: [kvm-devel] [PATCH 1/6] Use correct
types to enable > 2G support"):
> The alternative is to change all the places that assume phys_ram_base +
> PA which I don't like very much.
We would ideally like to do this for Xen, at least in the places we
care abou
When compiling KVM on 32 bit Linux there is a variable name collision in the
function emulator_write_emulated() with variable 'addr' which is a function
parameter and later redefined. The addr parameter for gva_to_gpa is therefore
uninitialized. Fixing this by renaming the function parameter to 'ad
SourceForge.net wrote:
> Bugs item #188, was opened at 2008-02-01 15:30
> Message generated for change (Tracker Item Submitted) made by Item Submitter
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=188&group_id=180599
>
> Please note that this
Michael Tokarev wrote:
> Amit Shah wrote:
[]
>>> With 2.6.23 and vanilla kvm modules, while from X, it opens the
>>> "virtual console" (an X window), but that console is entirely
>>> empty (black), and nothing more happens. I can Ctrl+C the original
>>> process, but nothing more.
>>>
>>> With 2.6.
Ian Jackson wrote:
> Anthony Liguori writes ("[Qemu-devel] Re: [kvm-devel] [PATCH 1/6] Use correct
> types to enable > 2G support"):
>
>> The alternative is to change all the places that assume phys_ram_base +
>> PA which I don't like very much.
>>
>
> We would ideally like to do this for
On Fri, Feb 01, 2008 at 11:53:02AM -0600, Anthony Liguori wrote:
> Ian Jackson wrote:
> > Anthony Liguori writes ("[Qemu-devel] Re: [kvm-devel] [PATCH 1/6] Use
> > correct types to enable > 2G support"):
> >
> >> The alternative is to change all the places that assume phys_ram_base +
> >> PA w
Paul Brook wrote:
>>> I agree with the fact that ram_size should be 64 bit. Maybe each
>>> machine could test the value and emit an error message if it is too
>>> big. Maybe an uint64_t would be better though.
>>>
>> uint64_t is probably more reasonable. I wouldn't begin to know what the
>>
On Fri, 1 Feb 2008, Robin Holt wrote:
> Maybe I haven't looked closely enough, but let's start with some common
> assumptions. Looking at do_wp_page from 2.6.24 (I believe that is what
> my work area is based upon). On line 1559, the function begins being
> declared.
Aah I looked at the wrong f
Argh. Did not see this soon enougn. Maybe this one is better since it
avoids the additional unlocks?
On Fri, 1 Feb 2008, Robin Holt wrote:
> do_wp_page can reach the _end callout without passing the _begin
> callout. This prevents making the _end unles the _begin has also
> been made.
>
> Inde
On Fri, 1 Feb 2008, Robin Holt wrote:
> OK. Now that release has been moved, I think I agree with you that the
> down_write(mmap_sem) can be used as our lock again and still work for
> Jack. I would like a ruling from Jack as well.
Talked to Jack last night and he said its okay.
-
On Fri, 1 Feb 2008, Robin Holt wrote:
> Currently, it is calling mmu_notifier _begin and _end under the
> i_mmap_lock. I _THINK_ the following will make it so we could support
> __xip_unmap (although I don't recall ever seeing that done on ia64 and
> don't even know what the circumstances are for
On Fri, 2008-02-01 at 13:07 -0600, Nathan Lynch wrote:
> Hollis Blanchard wrote:
> > --- a/arch/powerpc/kernel/asm-offsets.c
> > +++ b/arch/powerpc/kernel/asm-offsets.c
> > @@ -22,6 +22,7 @@
> > #include
> > #include
> > #include
> > +#include
> > #ifdef CONFIG_PPC64
> > #include
> > #in
On Fri, 1 Feb 2008, Andrea Arcangeli wrote:
> Note that my #v5 doesn't require to increase the page count all the
> time, so GRU will work fine with #v5.
But that comes with the cost of firing invalidate_page for every page
being evicted. In order to make your single invalidate_range work withou
Hollis Blanchard wrote:
> --- a/arch/powerpc/kernel/asm-offsets.c
> +++ b/arch/powerpc/kernel/asm-offsets.c
> @@ -22,6 +22,7 @@
> #include
> #include
> #include
> +#include
> #ifdef CONFIG_PPC64
> #include
> #include
> @@ -328,5 +329,31 @@ int main(void)
>
> DEFINE(PGD_TABLE_SIZ
Daniel P. Berrange wrote:
> On Fri, Feb 01, 2008 at 11:53:02AM -0600, Anthony Liguori wrote:
>
>> Ian Jackson wrote:
>>
>>> Anthony Liguori writes ("[Qemu-devel] Re: [kvm-devel] [PATCH 1/6] Use
>>> correct types to enable > 2G support"):
>>>
>>>
The alternative is to change
This removes -DCONFIG_X86 and installs asm/kvm.h. Otherwise, it's impossible
to build an application based on a make install of libkvm.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/configure b/configure
index 6b20c2f..418dbea 100755
--- a/configure
+++ b/configure
@@ -94,7 +94
Previously, the BIOS would probe the CPUs for SMP guests. This tends to be
very unreliably because of startup timing issues. By passing the number of
CPUs in the CMOS, the BIOS can detect the number of CPUs much more reliably.
Since v1, I've incorporated Fabrice's feedback so this is now a 1-lin
KVM supports the ability to use ACPI to shutdown guests. In order to enable
this requires some fixes to be able to generate the SCI interrupt and the
appropriate plumbing.
This patch hasn't changed since v1.
Index: qemu/hw/acpi.c
==
KVM supports more than 2GB of memory for x86_64 hosts. The following patch
fixes a number of type related issues where int's were being used when they
shouldn't have been. It also introduces CMOS support so the BIOS can build
the appropriate e820 tables.
For v2 of this page, I've moved ram_addr_
KVM is a Linux interface for providing userspace interfaces for accelerated
virtualization. It has been included since 2.6.20 and supports Intel VT and
AMD-V. Ports are under way for ia64, embedded PowerPC, and s390.
This set of patches provide basic support for KVM in QEMU. It does not include
This was never corrected during the ram_alloc() conversion.
Index: qemu/hw/pc.c
===
--- qemu.orig/hw/pc.c 2008-02-01 10:01:47.0 -0600
+++ qemu/hw/pc.c2008-02-01 10:57:01.0 -0600
@@ -869,7 +869,7 @@
} els
Avi Kivity wrote:
> From: Avi Kivity <[EMAIL PROTECTED]>
>
> Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
>
Can you also add one for qemu-kvm-x86.c?
Regards,
Anthony Liguori
-
This SF.net email is sponsored by: Microsof
And attached is v2 which updates both uses of ram_size instead of just
the one :-)
Regards,
Anthony Liguori
Anthony Liguori wrote:
This was never corrected during the ram_alloc() conversion.
Index: qemu/hw/pc.c
===
--- qemu.orig
Michael Tokarev wrote:
> Amit Shah wrote:
>
>> On Friday 01 February 2008 13:30:03 Michael Tokarev wrote:
[]
>>> With 2.6.23 and vanilla kvm modules, while from X, it opens the
>>> "virtual console" (an X window), but that console is entirely
>>> empty (black), and nothing more happens. I can Ctr
> virtio could still be made to work with map cache. You would just have
> to change it to be able to map more than one page contiguously. As I
> mentioned though, it just starts getting ugly.
That's why you should be using the cpu_physical_memory_rw routines :-)
Anything that assume large line
On Fri, 1 Feb 2008, Robin Holt wrote:
> We are getting this callout when we transition the pte from a read-only
> to read-write. Jack and I can not see a reason we would need that
> callout. It is causing problems for xpmem in that a write fault goes
> to get_user_pages which gets back to do_wp_
The -daemonize option is too restrictive when using with SDL. It also switches
the working directory to / too early which causes block devices with a relative
path to fail.
The -daemonize option is needed for my regression testing so I've included this
patch in the series.
This patch hasn't chan
Christoph,
The following code in do_wp_page is a problem.
We are getting this callout when we transition the pte from a read-only
to read-write. Jack and I can not see a reason we would need that
callout. It is causing problems for xpmem in that a write fault goes
to get_user_pages which gets b
On Fri, Feb 01, 2008 at 03:19:32PM -0800, Christoph Lameter wrote:
> On Fri, 1 Feb 2008, Robin Holt wrote:
>
> > We are getting this callout when we transition the pte from a read-only
> > to read-write. Jack and I can not see a reason we would need that
> > callout. It is causing problems for x
On Fri, 1 Feb 2008, Robin Holt wrote:
> On Fri, Feb 01, 2008 at 03:19:32PM -0800, Christoph Lameter wrote:
> > On Fri, 1 Feb 2008, Robin Holt wrote:
> >
> > > We are getting this callout when we transition the pte from a read-only
> > > to read-write. Jack and I can not see a reason we would nee
On Fri, Feb 01, 2008 at 04:05:08PM -0800, Christoph Lameter wrote:
> On Fri, 1 Feb 2008, Robin Holt wrote:
>
> > On Fri, Feb 01, 2008 at 03:19:32PM -0800, Christoph Lameter wrote:
> > > On Fri, 1 Feb 2008, Robin Holt wrote:
> > >
> > > > We are getting this callout when we transition the pte from
On Fri, Feb 01, 2008 at 06:21:45PM -0600, Robin Holt wrote:
> On Fri, Feb 01, 2008 at 04:05:08PM -0800, Christoph Lameter wrote:
> > Are you saying that you get the callback when transitioning from a read
> > only to a read write pte on the *same* page?
>
> I believe that is what we saw. We have
65 matches
Mail list logo
