On Tue, Oct 9, 2012 at 5:04 PM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
Hi,
sorry for the delayed answer.
On Sat, Sep 29, 2012 at 11:13:04AM +, Blue Swirl wrote:
The -dimm option is supposed to specify the dimm/memory layout, and not
create
any devices.
On Wed, Oct 10, 2012 at 3:07 PM, Peter Maydell peter.mayd...@linaro.org wrote:
From: Christoffer Dall cd...@cs.columbia.edu
Add basic support for KVM on ARM architecture.
Signed-off-by: Christoffer Dall cd...@cs.columbia.edu
[PMM: Minor tweaks and code cleanup, switch to ONE_REG]
Am 12.10.2012 23:53, schrieb Javier Guerra Giraldez:
On Fri, Oct 12, 2012 at 3:56 PM, Lukas Laukamp lu...@laukamp.me wrote:
I think that it must be possible to create an image with a size like the
used space + a few hundret MB with metadata or something like that.
the 'best' way to do it is
On 13 October 2012 10:09, Blue Swirl blauwir...@gmail.com wrote:
On Wed, Oct 10, 2012 at 3:07 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
From: Christoffer Dall cd...@cs.columbia.edu
Add basic support for KVM on ARM architecture.
+#include device_tree.h
Is this used?
Don't think
On Fri, Oct 12, 2012 at 09:18:54PM +0800, Asias He wrote:
Hello Michael,
Thanks for the review!
On 10/11/2012 08:41 PM, Michael S. Tsirkin wrote:
On Tue, Oct 09, 2012 at 04:05:18PM +0800, Asias He wrote:
vhost-blk is an in-kernel virito-blk device accelerator.
Due to lack of proper
Am 13.10.2012 12:28, schrieb Lukas Laukamp:
Am 12.10.2012 23:53, schrieb Javier Guerra Giraldez:
On Fri, Oct 12, 2012 at 3:56 PM, Lukas Laukamp lu...@laukamp.me wrote:
I think that it must be possible to create an image with a size like
the
used space + a few hundret MB with metadata or
Hello,
Wanted to get a clarification about KVM_MAX_VCPUS(currently set to 254)
in kvm_host.h file. The kvm_vcpu *vcpus array is sized based on KVM_MAX_VCPUS.
(i.e. a max of 254 elements in the array).
An 8bit APIC id should allow for 256 ID's. Reserving one for Broadcast should
leave 255
*** warning: this RFC patch series is only compile-tested ***
We need a way to specify the address at which we expect VMs to access
the interrupt controller (both the emulated distributor and the hardware
interface supporting virtualization). User space should decide on this
address as user
Used to initialize the in-kernel interrupt controller. On ARM we need to
map the virtual generic interrupt controller (vGIC) into Hyp the guest's
physicall address space so the guest can access the virtual cpu
interface. This must be done after the IRQ chips is create and after a
base address has
On ARM (and possibly other architectures) some bits are specific to the
model being emulated for the guest and user space needs a way to tell
the kernel about those bits. An example is mmio device base addresses,
where KVM must know the base address for a given device to properly
emulate mmio
We need this two factor initialization step to support a sane user space
initialization of the emulated model. We simply follow the names of the
ioctls for the internal vgic implementation steps and check if we have
everything we need on the host side when we create the vgic and set up
the rest
On 10/13/2012 06:29 PM, Chegu Vinod wrote:
Hello,
Wanted to get a clarification about KVM_MAX_VCPUS(currently set to 254)
in kvm_host.h file. The kvm_vcpu *vcpus array is sized based on
KVM_MAX_VCPUS.
(i.e. a max of 254 elements in the array).
An 8bit APIC id should allow for 256
12 matches
Mail list logo
