On Tue, 2010-11-16 at 10:23 +0800, Huang Ying wrote:
> Author: Max Asbock
>
> Add command x-gpa2hva to translate guest physical address to host
> virtual address. Because gpa to hva translation is not consistent, so
> this command is only used for debugging.
>
> The x-gpa2hva command provides on
(2010/11/18 22:06), Avi Kivity wrote:
On 11/18/2010 07:15 AM, Takuya Yoshikawa wrote:
We can also use this to selectively write protect pages to reduce unwanted page
faults in the future.
Looks like a good approach. Any measurements?
OK, I'll do some tests to select a right approach.
P
We should flush all tlbs after drop spte on sync_page path since:
Quote from Avi:
| sync_page
| drop_spte
| kvm_mmu_notifier_invalidate_page
| kvm_unmap_rmapp
| spte doesn't exist -> no flush
| page is freed
| guest can write into freed page?
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/pagi
We just need flush tlb if overwrite a writable spte with a read-only one.
And we should move this operation to set_spte() for sync_page path
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 20 +---
1 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/arch/x86
From: Lai Jiangshan
Rename it to fit its sense better
Signed-off-by: Lai Jiangshan
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |8
arch/x86/kvm/paging_tmpl.h | 10 +-
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/a
Remove it since we can jude it by using sp->unsync
Signed-off-by: Xiao Guangrong
---
arch/x86/include/asm/kvm_host.h |2 +-
arch/x86/kvm/mmu.c |8
arch/x86/kvm/paging_tmpl.h |5 ++---
3 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/arch/x86/i
Introduce a common function to map invalid gpte
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |3 --
arch/x86/kvm/paging_tmpl.h | 71 +++-
2 files changed, 37 insertions(+), 37 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/k
Quote from Avi:
| I don't think we need to flush immediately; set a "tlb dirty" bit somewhere
| that is cleareded when we flush the tlb. kvm_mmu_notifier_invalidate_page()
| can consult the bit and force a flush if set.
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/paging_tmpl.h |4 ++--
On 19.11.2010, at 07:24, Takuya Yoshikawa wrote:
> (2010/11/19 15:01), Yang Rui Rui wrote:
>> Hi,
>>
>> I searched the archive found some discutions about this, not fixed yet?
>> could someone tell, is g4 kvm available now?
>
> Hi, (added kvm-ppc to Cc)
>
> I'm using g4 (Mac mini box) to run K
On 11/16/2010 04:17 PM, Alexander Graf wrote:
On 16.11.2010, at 15:15, Avi Kivity wrote:
> On 11/16/2010 03:19 PM, Alexander Graf wrote:
>> >>>
>> >>
>> >> Rewriting it to use inb / stos works (jecxz ; insb; loop doesn't) so
it looks like a kernel bug in insb emulation.
>> >>
>> >
>> >
On Fri, Nov 19, 2010 at 05:05:38PM +0800, Xiao Guangrong wrote:
> Quote from Avi:
> | I don't think we need to flush immediately; set a "tlb dirty" bit somewhere
> | that is cleareded when we flush the tlb. kvm_mmu_notifier_invalidate_page()
> | can consult the bit and force a flush if set.
>
>
On Thu, Nov 18, 2010 at 07:09:08PM +0200, Michael S. Tsirkin wrote:
> Store irq routing table pointer in the irqfd object,
> and use that to inject MSI directly without bouncing out to
> a kernel thread.
>
> While we touch this structure, rearrange irqfd fields to make fastpath
> better packed for
>>> On 11/19/2010 at 10:54 AM, in message <20101119155427.ga20...@amt.cnet>,
Marcelo Tosatti wrote:
> On Thu, Nov 18, 2010 at 07:09:08PM +0200, Michael S. Tsirkin wrote:
>> Store irq routing table pointer in the irqfd object,
>> and use that to inject MSI directly without bouncing out to
>> a ker
Hello,
I need to limit the port speed of a VM to 10 mbps ( or 5 mbps if it's possible).
What's the way of doing so?
Regards
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordo
On Fri, Nov 19, 2010 at 2:47 PM, hadi golestani
wrote:
> Hello,
> I need to limit the port speed of a VM to 10 mbps ( or 5 mbps if it's
> possible).
> What's the way of doing so?
tc
check http://lartc.org/howto/lartc.qdisc.html
--
Javier
--
To unsubscribe from this list: send the line "unsub
When a devices is driven by userspace (like in the cases of KVM's
device assignment) it's essential to provide proper PCI error handling
support to the corresponding driver.
Implementation
==
The PCI error stub driver is implemented on top of the uio framework.
PCI errors are reporte
v3:
- Rework to avoid introducing conflicts with qemu.git hw/pci
- Drop capability lookup table
- Add back minimal device assignment PM, EXP, X, VPD, VNDR
capabilities
This version should do a much better job at not introducing new
differences between qemu-kvm.git and qemu.git hw/pci. The
Make use of wmask, just like the rest of config space.
This duplicates code in pci_default_write_config, but we plan to get
rid of this function anyway, so avoid the code churn.
Signed-off-by: Alex Williamson
---
hw/pci.c | 19 ---
1 files changed, 8 insertions(+), 11 deletio
This interface doesn't make much sense, adding a capability can
take care of everything, just provide a means to register
capability read/write handlers.
Device assignment does it's own thing, so requires a couple
ugly hacks that will be cleaned by subsequent patches.
Signed-off-by: Alex Williams
Convert to use common pci_add_capabilities() rather than creating
our own mess.
Signed-off-by: Alex Williamson
---
hw/device-assignment.c | 112 +++-
1 files changed, 63 insertions(+), 49 deletions(-)
diff --git a/hw/device-assignment.c b/hw/device-
Capabilities are allocated in bytes, so we can track both whether
a byte is used and by what capability in the same structure.
Remove pci_reserve_capability() as there are no users, remove
pci_access_cap_config() since it's now a trivial lookup.
Signed-off-by: Alex Williamson
---
hw/device-ass
Capabilities aren't required to be contiguous, so cap.length never
really made much sense. Likewise, cap.start is mostly meaningless
too. Both of these are better served by the capability map. We
can also get rid of cap.supported, since it's really now unused
and redundant with flag in the statu
Now that common PCI code doesn't have a hangup on capabilities
being contiguous, move assigned device capabilities to match
their offset on physical hardware. This helps for drivers that
assume a capability configuration and don't bother searching.
We can also remove several calls to assigned_dev
Drivers can break these out on their own if they need to.
Signed-off-by: Alex Williamson
---
hw/device-assignment.c | 16 -
hw/pci.c | 61 ++--
hw/pci.h | 19 ---
3 files changed, 13 insertions
We can figure out the capability being touched much more quickly
and efficiently with the config_map. Use it.
Signed-off-by: Alex Williamson
---
hw/device-assignment.c | 32 +++-
1 files changed, 19 insertions(+), 13 deletions(-)
diff --git a/hw/device-assignment
Some drivers depend on finding capabilities like power management,
PCI express/X, vital product data, or vendor specific fields. Now
that we have better capability support, we can pass more of these
tables through to the guest. Note that VPD and VNDR are direct pass
through capabilies, the rest a
On Tue, 2010-11-16 at 15:05 +0100, Bernhard Kohl wrote:
> This is necessary because during reboot of a VM the assigned devices
> continue DMA transfers which causes memory corruption.
>
> Signed-off-by: Thomas Ostler
> Signed-off-by: Bernhard Kohl
> ---
> Changes v1 -> v2:
> - use defined macros
Hello,
you may also have a look at VDE (Virtual Distributed Ethernet). You can
connect your VMs to virtual switches and then use the tool
'wirefilter'[1] to modify different attributes (bandwidth, loss, delay,
etc) of the virtual network.
[1] http://wiki.virtualsquare.org/wiki/index.php/VDE
Rega
On Tue, Nov 16, 2010 at 09:22:45AM +0200, Gleb Natapov wrote:
> On Mon, Nov 15, 2010 at 09:52:19PM -0500, Kevin O'Connor wrote:
> > I also have an ulterior motive here. If the boot order is exposed as
> > a newline separated list via an entry in QEMU_CFG_FILE_DIR, then this
> > becomes free for co
On Mon, Nov 15, 2010 at 08:29:24PM +, Blue Swirl wrote:
> 2010/11/15 Gleb Natapov :
> > On Sun, Nov 14, 2010 at 10:50:13PM +, Blue Swirl wrote:
> >> On Sun, Nov 14, 2010 at 3:39 PM, Gleb Natapov wrote:
> >> >
> >> > Signed-off-by: Gleb Natapov
> >> > ---
> >> > hw/fw_cfg.c | 14 +++
Hi,
I'm not sure if this is the correct venue for this question; feel
free to redirect.
When I start debian or ubuntu guests on a debian host running KVM
0.12.5, my guests kernel-panic immediately after bootup -- the OOM
killer kills every process on the s
31 matches
Mail list logo