On Sat, 8 Feb 2014 08:51:57 +0100 Andi Kleen wrote:
> kvm_rebooting is referenced from assembler code, thus
> needs to be visible.
So I read the gcc page and looked at the __visible definition but I
still don't really get it. What goes wrong if the __visible isn't
present on these referenced-f
On Mon, 2014-02-10 at 17:12 -0600, Scott Wood wrote:
> On Mon, 2014-02-10 at 15:45 -0700, Alex Williamson wrote:
> > On Sat, 2014-02-08 at 18:29 +0100, Antonios Motakis wrote:
> > > VFIO returns a file descriptor which we can use to manipulate the memory
> > > regions of the device. Since some memo
On Mon, 2014-02-10 at 15:45 -0700, Alex Williamson wrote:
> On Sat, 2014-02-08 at 18:29 +0100, Antonios Motakis wrote:
> > VFIO returns a file descriptor which we can use to manipulate the memory
> > regions of the device. Since some memory regions we cannot mmap due to
> > security concerns, we al
On Sat, 2014-02-08 at 18:29 +0100, Antonios Motakis wrote:
> VFIO returns a file descriptor which we can use to manipulate the memory
> regions of the device. Since some memory regions we cannot mmap due to
> security concerns, we also allow to read and write to this file descriptor
> directly.
>
Am 10.02.2014 11:21, schrieb Eduardo Habkost:
> +static const TypeInfo x86_cpu_host_type_info = {
> +.name = CPU_CLASS_NAME("host"),
> +.parent = TYPE_X86_CPU,
> +.instance_size = sizeof(X86CPU),
> +.instance_init = x86_cpu_instance_init_host,
> +.abstract = false,
> +.class
On Sat, 2014-02-08 at 18:29 +0100, Antonios Motakis wrote:
> A VFIO userspace driver will start by opening the VFIO device
> that corresponds to an IOMMU group, and will use the ioctl interface
> to get the basic device info, such as number of memory regions and
> interrupts, and their properties.
On Mon, 2014-02-10 at 13:09 -0800, Roland Dreier wrote:
> Hi everyone,
>
> I'm updating my dev environment to use the shiny new vfio
> infrastructure for PCI assignment to kvm guests, and I'm not able to
> do what I used to do with the old-school KVM passthrough. In
> particular, I have, say, a t
Hi everyone,
I'm updating my dev environment to use the shiny new vfio
infrastructure for PCI assignment to kvm guests, and I'm not able to
do what I used to do with the old-school KVM passthrough. In
particular, I have, say, a two-port QLogic adapter that looks like:
82:00.0 0200: 1077:8030
On Sat, 2014-02-08 at 18:29 +0100, Antonios Motakis wrote:
> The ARM SMMU driver expects the IOMMU_EXEC flag, otherwise it will
> set the page tables for a device as XN (execute never). This affects
> devices such as the ARM PL330 DMA Controller, which fails to operate
> if the XN flag is set on th
Hi Vadim & Yan,
On Sun, 2014-02-09 at 22:35 +1100, Vadim Rozenfeld wrote:
> On Sun, 2014-02-09 at 11:24 +0200, Yan Vugenfirer wrote:
> > Hi Nicholas,
> >
> > Adding Vadim Rozenfeld who wrote the virtio-scsi driver.
> >
> > Best regards,
> > Yan.
> >
> > On Feb 7, 2014, at 10:14 PM, Nicholas A.
https://bugzilla.kernel.org/show_bug.cgi?id=69491
--- Comment #6 from Kashyap Chamarthy ---
Created attachment 125521
--> https://bugzilla.kernel.org/attachment.cgi?id=125521&action=edit
Successful stderr of `dmesg` on L0 with Kernel 3.14.0-0.rc1.git4.1.fc21.x86_64
I just tested with this Kern
Am 16.12.2013 15:12, schrieb James Hogan:
> From: Sanjay Lal
>
> Implement the main KVM arch API for MIPS.
>
> Signed-off-by: Sanjay Lal
> Signed-off-by: James Hogan
> Cc: Aurelien Jarno
> Cc: Gleb Natapov
> Cc: Paolo Bonzini
> ---
> Changes in v2:
> - Expand commit message
> - Checkpatch
Hi
Please, send any topic that you are interested in covering.
Agenda:
* [Qemu-devel] [PATCH V17 00/11] Add support for binding guest numa
nodes
Any news about this? (Vinod)
* Should we change anything to get more people to sign for the call?
There hasn't been a call in quite a long time.
Register separate QOM classes for each x86 CPU model.
This will allow management code to more easily probe what each CPU model
provides, by simply creating objects using the appropriate class name,
without having to restart QEMU.
This also allows us to eliminate the qdev_prop_set_globals_for_type
On Mon, 2014-02-10 at 08:21 +, Zhang, Yang Z wrote:
> Hi Vadim,
>
> Do you know the latest status of Hyper-v Enlightenments supporting in KVM?
> Like how many Hyper-v interfaces are supported in KVM?
Hi Yang,
There is no many at the moment. KVM currently supports the following
Hyper-V fea
On Mon, 10 Feb 2014 01:23:37 +0100
Andreas Färber wrote:
> Am 31.01.2014 19:13, schrieb Eduardo Habkost:
> > Register separate QOM classes for each x86 CPU model.
> >
> > This will allow management code to more easily probe what each CPU model
> > provides, by simply creating objects using the a
https://bugzilla.kernel.org/show_bug.cgi?id=69491
robert...@intel.com changed:
What|Removed |Added
CC||robert...@intel.com
--- Comment #5 f
On Mon, Feb 10, 2014 at 06:19:58AM -0200, Eduardo Habkost wrote:
> On Mon, Feb 10, 2014 at 01:23:37AM +0100, Andreas Färber wrote:
> [...]
> > > /**
> > > * X86CPUClass:
> > > * @parent_realize: The parent class' realize handler.
> > > @@ -49,6 +52,16 @@ typedef struct X86CPUClass {
> > >
Hi Vadim,
Do you know the latest status of Hyper-v Enlightenments supporting in KVM? Like
how many Hyper-v interfaces are supported in KVM?
best regards
yang
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo i
On Mon, Feb 10, 2014 at 01:23:37AM +0100, Andreas Färber wrote:
[...]
> > /**
> > * X86CPUClass:
> > * @parent_realize: The parent class' realize handler.
> > @@ -49,6 +52,16 @@ typedef struct X86CPUClass {
> > CPUClass parent_class;
> > /*< public >*/
> >
> > +/* CPU model def
20 matches
Mail list logo
