From: Xiantao Zhang [EMAIL PROTECTED]
An uniform entry kvm_vps_entry is added for
vps_sync_write/read, vps_resume_handler/guest,
and branches to differnt PAL service according to the offset.
Singed-off-by: Anthony Xu [EMAIL PROTECTED]
Signed-off-by: Xiantao Zhang [EMAIL PROTECTED]
Signed-off-by:
From: Glauber Costa [EMAIL PROTECTED]
memory holes are totally evil. Right now they work for some basic tests,
but had never been stressed enough. Using memory holes leaves open questions
like:
* what happens if a area being registered span two slots?
* what happens if there is already data in
From: Glauber Costa [EMAIL PROTECTED]
By analysing phys_offset, we know whether a region is an mmio region
or not. If it is, we don't want to have kvm caring about it, so just
return.
Signed-off-by: Glauber Costa [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git
From: Glauber Costa [EMAIL PROTECTED]
Signed-off-by: Glauber Costa [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/libkvm/libkvm.c b/libkvm/libkvm.c
index f7a7fdd..88d3f5d 100644
--- a/libkvm/libkvm.c
+++ b/libkvm/libkvm.c
@@ -508,6 +508,18 @@ void
Hi all,
The initial passthrough/VT-d patches have been in kvm, it's time to
enhance it, and push them into 2.6.28.
Following is the remaining passthrough/VT-d tasks list:
- Multiple devices assignment (WIP)
- MSI support (WIP)
- MTRR/PAT support of EPT (WIP)
-
On Wednesday 24 September 2008 14:15:15 Han, Weidong wrote:
Hi all,
The initial passthrough/VT-d patches have been in kvm, it's time to enhance
it, and push them into 2.6.28.
Some supplements:
Following is the remaining passthrough/VT-d tasks list:
- Multiple devices assignment
* On Wednesday 24 Sep 2008 13:21:25 Han, Weidong wrote:
Amit Shah wrote:
- Add dummy driver to hide/unbind passthrough device from
host kernel
This isn't needed; we currently don't assign the device to the guest
if we find that a driver is already loaded. I intend to change it to
Han, Weidong wrote:
Hi all,
The initial passthrough/VT-d patches have been in kvm, it's time to
enhance it, and push them into 2.6.28.
- Shared Interrupt support
Shared guest interrupts is a prerequisite for merging into mainline.
Without this, device assignment is useless in
Amit Shah wrote:
* On Wednesday 24 Sep 2008 13:21:25 Han, Weidong wrote:
Amit Shah wrote:
- Add dummy driver to hide/unbind passthrough device from
host kernel
This isn't needed; we currently don't assign the device to the guest
if we find that a driver is already loaded. I
Yang, Sheng wrote:
- MSI support (WIP)
- MTRR/PAT support of EPT (WIP)
- MTRR/PAT support of shadow (WIP)
- Basic FLR support (WIP)
Above four are my works. All of them work now. But more job should be done to
polish the patches. And the main part of
Han, Weidong wrote:
- Add dummy driver to hide/unbind passthrough device from host
kernel
Maybe this can be implemented at the modprobe/hotplug level.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm
On Wednesday 24 September 2008 16:34:22 Avi Kivity wrote:
Han, Weidong wrote:
Hi all,
The initial passthrough/VT-d patches have been in kvm, it's time to
enhance it, and push them into 2.6.28.
- Shared Interrupt support
Shared guest interrupts is a prerequisite for merging
On Wednesday 24 September 2008 16:38:35 Avi Kivity wrote:
Yang, Sheng wrote:
- MSI support (WIP)
- MTRR/PAT support of EPT (WIP)
- MTRR/PAT support of shadow (WIP)
- Basic FLR support (WIP)
Above four are my works. All of them work now. But more job
Amit Shah wrote:
I'd say we have about 3 weeks to get things in.
How do you figure? 2.6.26 was released July 13, we're more than 2.5
months later.
Furthermore, I'm not queueing untested patches for 2.6.28 at this time.
--
error compiling committee.c: too many arguments to function
--
Avi Kivity wrote:
Han, Weidong wrote:
- Add dummy driver to hide/unbind passthrough device from host
kernel
Maybe this can be implemented at the modprobe/hotplug level.
I think so.
Randy (Weidong)
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a
Han, Weidong wrote:
We had some discussion on this few months ago. Currently, users need to
remove device driver before assignment. If there are more than one same
type devices, removing driver makes them cannot work at the same time,
even though user just want to assign one of them to guest.
Yang, Sheng wrote:
Shared guest interrupts is a prerequisite for merging into mainline.
Without this, device assignment is useless in anything but a benchmark
scenario. I won't push device assignment for 2.6.28 without it.
Shared host interrupts are a different matter; which one did you mean?
Han, Weidong wrote:
Currently #include linux/intel-iommu.h is not needed in
virt/kvm/kvm_main.c. What's more, this inclusion may result in
compilation error in other architecture.
Applied, but please also fix intel-iommu.h to compile on all archs.
--
error compiling committee.c: too many
Anthony Liguori wrote:
This patch implements a simple fd pool to allow many AIO requests with
posix-aio. The result is significantly improved performance (identical to that
reported for linux-aio) for both cache=on and cache=off.
The fundamental problem with posix-aio is that it limits itself
On Wednesday 24 September 2008 16:53:15 Avi Kivity wrote:
Yang, Sheng wrote:
Shared guest interrupts is a prerequisite for merging into mainline.
Without this, device assignment is useless in anything but a benchmark
scenario. I won't push device assignment for 2.6.28 without it.
Avi Kivity wrote:
Han, Weidong wrote:
Currently #include linux/intel-iommu.h is not needed in
virt/kvm/kvm_main.c. What's more, this inclusion may result in
compilation error in other architecture.
Applied, but please also fix intel-iommu.h to compile on all archs.
Avi,
Current
Han, Weidong wrote:
Avi Kivity wrote:
Han, Weidong wrote:
- Add dummy driver to hide/unbind passthrough device from host
kernel
Maybe this can be implemented at the modprobe/hotplug level.
I think so.
I'm not sure now -- after I saw the point about a
Han, Weidong wrote:
Avi Kivity wrote:
Han, Weidong wrote:
Currently #include linux/intel-iommu.h is not needed in
virt/kvm/kvm_main.c. What's more, this inclusion may result in
compilation error in other architecture.
Applied, but please also fix intel-iommu.h to compile on
Hi,
This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
really gets out of hand when you boot say a 64GB guest.
Cheers,
Jes
Cap code_gen_buffer_size on ia64 - it quickly goes out of hand otherwise
when booting larger guests.
Signed-off-by: Jes Sorensen [EMAIL PROTECTED]
---
Yang, Sheng wrote:
We only have three pci interrupts at this point (though this could be
easily extended); if you start the guest with a non-trivial number of
devices, you will have shared guest interrupts.
(of course, when I pointed this out during review, people said it could
be done later,
Glauber Costa wrote:
Call it as a special case for cpu 0 creation. This removes
a piece of kvm code from raw qemu.
+void kvm_init_new_ap(int cpu, CPUState *env)
+{
+if (!cpu)
+kvm_init_ap();
+
+pthread_create(vcpu_info[cpu].thread, NULL, ap_main_loop, env);
+
+while
On Wednesday 24 September 2008 17:22:53 Avi Kivity wrote:
Yang, Sheng wrote:
We only have three pci interrupts at this point (though this could be
easily extended); if you start the guest with a non-trivial number of
devices, you will have shared guest interrupts.
(of course, when I
* On Wednesday 24 Sep 2008 14:08:14 Han, Weidong wrote:
Amit Shah wrote:
* On Wednesday 24 Sep 2008 13:21:25 Han, Weidong wrote:
Amit Shah wrote:
- Add dummy driver to hide/unbind passthrough device from
host kernel
This isn't needed; we currently don't assign the device to
* On Wednesday 24 Sep 2008 14:16:47 Avi Kivity wrote:
Amit Shah wrote:
I'd say we have about 3 weeks to get things in.
How do you figure? 2.6.26 was released July 13, we're more than 2.5
months later.
A week for 2.6.28 to open and two weeks for the rc1 window.
Furthermore, I'm not
On Tuesday 23 September 2008 23:04:48 Jan Kiszka wrote:
Yang, Sheng wrote:
On Friday 19 September 2008 20:03:02 Jan Kiszka wrote:
LINT0 of the LAPIC can be used to route PIT events as NMI watchdog
ticks into the guest. This patch aligns the in-kernel irqchip emulation
with the user space
Amit Shah wrote:
* On Wednesday 24 Sep 2008 14:16:47 Avi Kivity wrote:
Amit Shah wrote:
I'd say we have about 3 weeks to get things in.
How do you figure? 2.6.26 was released July 13, we're more than 2.5
months later.
A week for 2.6.28 to open and two weeks for the rc1
Jes Sorensen wrote:
Hi,
This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
really gets out of hand when you boot say a 64GB guest.
ia64 doesn't codegen; why not set it to zero?
(and the phys_ram_size / 4 heuristic is ridiculous; code size doesn't
scale with guest size)
--
Avi Kivity wrote:
ia64 doesn't codegen; why not set it to zero?
(and the phys_ram_size / 4 heuristic is ridiculous; code size doesn't
scale with guest size)
That works too - I didn't really know this part too well, but I hit
the problem that I was unable to allocate the space because of 64
Alex Williamson wrote:
As requested, here's the follow-on to the 4G MTRR changes split into
functional bits.
[1/5] Rename variables to reflect what they're really reporting
[2/5] Reformat ram_probe() to match the rest of the code
[3/5] Add SMBIOS info for memory above 4G
[4/5] Fix the SMBIOS
Glauber Costa wrote:
You can't coalesce the registers which trigger device action. You'll
destroy latency and/or functionality.
which kills the goal of getting rid of explicit kvm code.
It's a fact that coalescing helps kvm but not qemu.
So maybe the solution here is to add
Avi Kivity wrote:
Jes Sorensen wrote:
Hi,
This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
really gets out of hand when you boot say a 64GB guest.
ia64 doesn't codegen; why not set it to zero?
How about this one then?
Jes
Do not allocate a code_gen buffer on ia64 given it
Jes Sorensen wrote:
Avi Kivity wrote:
Jes Sorensen wrote:
Hi,
This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
really gets out of hand when you boot say a 64GB guest.
ia64 doesn't codegen; why not set it to zero?
How about this one then?
Applied, thanks. Note qemu
Avi Kivity wrote:
Applied, thanks. Note qemu uses 4 spaces for intedenation. Talk to
your editor.
Even when it's a double indentation, ie 8 spaces?
Thats just plain sicko :-(
Jes
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
Marcelo Tosatti wrote:
KVM: PIC: enhance IPI avoidance
The PIC code makes little effort to avoid kvm_vcpu_kick(), resulting in
unnecessary guest exits in some conditions.
For example, if the timer interrupt is routed through the IOAPIC, IRR
for IRQ 0 will get set but not cleared, since the
Amit Shah wrote:
* On Wednesday 24 Sep 2008 14:08:14 Han, Weidong wrote:
Amit Shah wrote:
* On Wednesday 24 Sep 2008 13:21:25 Han, Weidong wrote:
Amit Shah wrote:
- Add dummy driver to hide/unbind passthrough device from
host kernel
This isn't needed; we currently don't assign the
Yang, Sheng wrote:
On Tuesday 23 September 2008 17:45:44 Gleb Natapov wrote:
On Tue, Sep 23, 2008 at 05:42:02PM +0800, Yang, Sheng wrote:
That is exactly what I am using. Run it with SMP hal and do
hibernate.
Oh... Finally found how to enable that hibernate option
And this hibernate
Jan Kiszka wrote:
After Windows' graphical installation phase I had a hanging guest. At
the same time I got
kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9
kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s
timeout
in the kernel log as well.
Dan Smith wrote:
Hi,
After hitting the pvclock-related issue, I recompiled my 2.6.27-rc6
kernel without CONFIG_KVM_CLOCK. It stays up far longer, but I see
the following guest crash when I stress it (with a source build):
Are you using 4K stacks? If so, please try with 8K stacks and
On Wed, Sep 24, 2008 at 02:40:18PM +0200, Jan Kiszka wrote:
Yang, Sheng wrote:
On Tuesday 23 September 2008 17:45:44 Gleb Natapov wrote:
On Tue, Sep 23, 2008 at 05:42:02PM +0800, Yang, Sheng wrote:
That is exactly what I am using. Run it with SMP hal and do
hibernate.
Oh... Finally
Avi Kivity wrote:
Jes Sorensen wrote:
Avi Kivity wrote:
Applied, thanks. Note qemu uses 4 spaces for intedenation. Talk to
your editor.
Even when it's a double indentation, ie 8 spaces?
Yes.
:-(
Well then we really should add something like this to every file in
qemu, since this
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 02:40:18PM +0200, Jan Kiszka wrote:
Yang, Sheng wrote:
On Tuesday 23 September 2008 17:45:44 Gleb Natapov wrote:
On Tue, Sep 23, 2008 at 05:42:02PM +0800, Yang, Sheng wrote:
That is exactly what I am using. Run it with SMP hal and do
hibernate.
On Wed, Sep 24, 2008 at 02:56:40PM +0200, Jan Kiszka wrote:
We should do something like this:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 046a91b..860e66d 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2826,10 +2826,20 @@ static int
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 02:56:40PM +0200, Jan Kiszka wrote:
We should do something like this:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 046a91b..860e66d 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2826,10 +2826,20 @@ static int
On Wed, Sep 24, 2008 at 03:11:36PM +0200, Jan Kiszka wrote:
OK, I just think we are not supposed to set GUEST_INTR_STATE_NMI without
cpu_has_virtual_nmis(). Otherwise looks reasonable. Have you tested
this? Does it make your 2003 power-off?
It does power-off, but hands during reboot.
On Wed, Sep 24, 2008 at 04:17:00PM +0300, Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:11:36PM +0200, Jan Kiszka wrote:
OK, I just think we are not supposed to set GUEST_INTR_STATE_NMI without
cpu_has_virtual_nmis(). Otherwise looks reasonable. Have you tested
this? Does it make your
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much earlier. BIOS hangs because CPU1 ignores SIPI.
--
Gleb.
--
To
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much earlier. BIOS hangs because CPU1 ignores SIPI.
That sounds like an
On Wed, Sep 24, 2008 at 03:33:13PM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much
Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much earlier. BIOS hangs because
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 04:17:00PM +0300, Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:11:36PM +0200, Jan Kiszka wrote:
OK, I just think we are not supposed to set GUEST_INTR_STATE_NMI without
cpu_has_virtual_nmis(). Otherwise looks reasonable. Have you tested
this? Does
Eduardo Habkost wrote:
This series adds compat code to allow enabling kvm_trace when building
KVM as an external module on older kernels.
The most hackish part is the last patch, that adds --with-kvm-trace to
configure and adds an include to a generated file on kernel/x86/Kbuild. It
doesn't
Eduardo Habkost wrote:
@@ -73,6 +73,8 @@ BEGIN { split(INIT_WORK tsc_khz desc_struct ldttss_desc64
desc_ptr \
}
}
+{ sub(/relay_open/, kvm_relay_open) }
+
I moved this bit into the compat_apis variable. Hope it still works.
--
error compiling committee.c: too many arguments to
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much earlier. BIOS hangs because CPU1 ignores SIPI.
Apropos APIC: I also
Avi Kivity wrote:
Anthony Liguori wrote:
dup()ing the fd on each request is unnecessary work; would be better
to cache the duped fd.
Yeah, I was concerned about this too. Ryan reran the fio benchmark and
the submission latency and completion latency were identical to the
linux-aio
Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote:
It does power-off, but hands during reboot. Looking at it right now.
After completing the RAM read-back from disk? This is where it hangs
Much earlier. BIOS hangs because
On Wed, Sep 24, 2008 at 03:19:47PM +0300, Avi Kivity wrote:
Index: kvm/arch/x86/kvm/irq.h
===
--- kvm.orig/arch/x86/kvm/irq.h
+++ kvm/arch/x86/kvm/irq.h
@@ -42,6 +42,7 @@ struct kvm_kpic_state {
u8 irr; /* interrupt
Avi Kivity wrote:
Amit Shah wrote:
* On Wednesday 24 Sep 2008 14:16:47 Avi Kivity wrote:
Amit Shah wrote:
I'd say we have about 3 weeks to get things in.
How do you figure? 2.6.26 was released July 13, we're more than 2.5
months later.
A week for 2.6.28 to open and two weeks for
On Wed, Sep 24, 2008 at 04:02:36PM +0300, Gleb Natapov wrote:
On Wed, Sep 24, 2008 at 02:56:40PM +0200, Jan Kiszka wrote:
We should do something like this:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 046a91b..860e66d 100644
--- a/arch/x86/kvm/vmx.c
+++
Marcelo Tosatti wrote:
and by register load from userspace, no?
Isnt that responsability of the guest?
I'm talking about a restore to previous state scenario. In this case we
want to disable any IPI avoidance in case it avoids a needed IPI.
Unacked IOAPIC interrupts are not
Amit Shah wrote:
* On Tuesday 23 Sep 2008 21:43:44 Anthony Liguori wrote:
Amit Shah wrote:
Signed-off-by: Amit Shah [EMAIL PROTECTED]
---
qemu/hw/isa.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu/hw/isa.h b/qemu/hw/isa.h
index 222e4f3..e4a1326 100644
Amit Shah wrote:
* On Tuesday 23 Sep 2008 22:00:32 Anthony Liguori wrote:
Amit Shah wrote:
diff --git a/qemu/Makefile.target b/qemu/Makefile.target
index 72f3db8..40eb273 100644
--- a/qemu/Makefile.target
+++ b/qemu/Makefile.target
@@ -616,6 +616,7 @@ OBJS+= ide.o pckbd.o ps2.o
Amit Shah wrote:
* On Tuesday 23 Sep 2008 22:01:10 Anthony Liguori wrote:
Amit Shah wrote:
Signed-off-by: Amit Shah [EMAIL PROTECTED]
---
kernel/x86/Kbuild |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/x86/Kbuild b/kernel/x86/Kbuild
index
Avi Kivity wrote:
Han, Weidong wrote:
- Add dummy driver to hide/unbind passthrough device from host
kernel
Maybe this can be implemented at the modprobe/hotplug level.
Wouldn't you just blacklist the devices in the host and call it a day?
Regards,
Anthony Liguori
--
To
Avi Kivity wrote:
Jes Sorensen wrote:
Avi Kivity wrote:
Jes Sorensen wrote:
Hi,
This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
really gets out of hand when you boot say a 64GB guest.
ia64 doesn't codegen; why not set it to zero?
How about this one then?
Applied,
Avi Kivity wrote:
Han, Weidong wrote:
Hi all,
The initial passthrough/VT-d patches have been in kvm,
it's time to enhance it, and push them into 2.6.28.
- Shared Interrupt support
Shared guest interrupts is a prerequisite for merging
into mainline. Without this, device
Anthony Liguori wrote:
It would seem better to replace #ifdef TARGET_IA64 with if
(kvm_enabled()).
Right. Committed.
--
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 [EMAIL
On Wed, 2008-09-24 at 14:07 +0300, Avi Kivity wrote:
The patches all look good, however renaming and reformatting will lead
to merge headaches later on. We haven't been good at working with bochs
bios upstream.
Can you peek in bochs upstream and see if it's worth merging? If not,
On 9/23/08, David Miller [EMAIL PROTECTED] wrote:
From: Blue Swirl [EMAIL PROTECTED]
Date: Tue, 23 Sep 2008 18:28:06 +0300
On 9/22/08, David Miller [EMAIL PROTECTED] wrote:
As he mentioned, the V8 rett instruction causes problems on V9 chips.
An opcode which was a V8
On 9/23/08, David Miller [EMAIL PROTECTED] wrote:
From: Blue Swirl [EMAIL PROTECTED]
Date: Tue, 23 Sep 2008 18:34:12 +0300
On 9/23/08, David Miller [EMAIL PROTECTED] wrote:
Sun4v systems come with Sun's hypervisor. Linux simply runs on top
of that, whether as a host or a guest.
On Wed, Sep 24, 2008 at 04:48:35PM +0300, Avi Kivity wrote:
Eduardo Habkost wrote:
This series adds compat code to allow enabling kvm_trace when building
KVM as an external module on older kernels.
The most hackish part is the last patch, that adds --with-kvm-trace to
configure and adds an
On 9/24/08, Blue Swirl [EMAIL PROTECTED] wrote:
On 9/23/08, David Miller [EMAIL PROTECTED] wrote:
From: Blue Swirl [EMAIL PROTECTED]
Date: Tue, 23 Sep 2008 18:28:06 +0300
On 9/22/08, David Miller [EMAIL PROTECTED] wrote:
As he mentioned, the V8 rett instruction causes
From: Blue Swirl [EMAIL PROTECTED]
Date: Wed, 24 Sep 2008 20:20:33 +0300
I see, also Qemu needs to use one more bit then. Does this mean that
even V8 code written specially may use these traps to call hypervisor?
No, V8 code should not set the extra bit. Only V9 code on a processor
which is
From: Blue Swirl [EMAIL PROTECTED]
Date: Wed, 24 Sep 2008 20:22:45 +0300
I'm not sure, but I think that hypervisor is not a real hypervisor
like the PROM version but one specially designed for Legion emulator.
No, it's the real deal.
All the real hardware device support is there.
And Legion
From: Blue Swirl [EMAIL PROTECTED]
Date: Wed, 24 Sep 2008 21:06:21 +0300
Now I found the relevant part in the manuals. The extra sun4v bit is
not taken into account from user mode, so we can't catch privileged to
hyperprivileged mode traps easily.
That's right, the top bit is ignored in user
On Wed, Sep 24, 2008 at 05:49:37PM +0300, Avi Kivity wrote:
Marcelo Tosatti wrote:
and by register load from userspace, no?
Isnt that responsability of the guest?
I'm talking about a restore to previous state scenario. In this case we
want to disable any IPI avoidance in case
Good morning,
Is it possible to establish a PPTP connection from a guest running Windows
2000 Professional SP4 to a remote machine running Windows Server 2003 using
user-mode networking?
It appears to me that the problem is that GRE protocol packets are not being
successfully transmitted. I
On Tuesday 23 September 2008 22:54:53 Amit Shah wrote:
From: Or Sagi [EMAIL PROTECTED]
From: Nir Peleg [EMAIL PROTECTED]
From: Amit Shah [EMAIL PROTECTED]
From: Ben-Ami Yassour [EMAIL PROTECTED]
From: Weidong Han [EMAIL PROTECTED]
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
With this
On Thursday 25 September 2008 12:54:46 Yang, Sheng wrote:
On Tuesday 23 September 2008 22:54:53 Amit Shah wrote:
From: Or Sagi [EMAIL PROTECTED]
From: Nir Peleg [EMAIL PROTECTED]
From: Amit Shah [EMAIL PROTECTED]
From: Ben-Ami Yassour [EMAIL PROTECTED]
From: Weidong Han [EMAIL
83 matches
Mail list logo
