const struct ivshmem_client_peer
> *peer)
> +{
> +unsigned vector;
> +int ret = 0;
> +
> +for (vector = 0; vector < peer->vectors_count; vector++) {
> + if (ivshmem_client_notify(client, peer, vector) < 0) {
> +ret = -1;
The ret&#x
vice *pci_dev,
> Error **errp)
> uint8_t *pci_conf;
> char *name;
> int r, i;
> +d->zero = mmap(NULL, IOTEST_MEMSIZE * 2, PROT_READ,
> + MAP_SHARED | MAP_ANONYMOUS, -1, 0);
> +
Do we need think about hotplugging pci-testdev ? I
On 2015/1/26 21:13, Gonglei (Arei) wrote:
> From: Gonglei
>
> In order to support to assign a boot order for
> vhost-scsi device, we should get the tpgt for
> user level (such as Qemu). and at present, we
> only support the minimum tpgt can boot.
>
Ping...
> Signed-o
the ivshmem code
> clearly
> need cleanup. I will try to address this in future patches when these first
> patches are ok.
>
>
If you can describe the steps of using example about
your ivshmem-client and ivshmem-server will be great IMHO.
Best regards,
-Gonglei
> --
> David
Hi,
> Subject: Re: [Qemu-devel] [PATCH v3 0/2] ivshmem: update documentation,
> add client/server tools
>
> Hello Gonglei,
>
> On 08/08/2014 11:30 AM, Gonglei (Arei) wrote:
> > If you can describe the steps of using example about
> > your ivshmem-client and ivs
; virt/kvm/ioapic.c | 50
> --
> virt/kvm/ioapic.h | 6 ++
> 3 files changed, 74 insertions(+), 2 deletions(-)
>
If this is a new version, please add a v2/v3 suffix and describe the changes at
those different versions .
Y
y, we don't have to set a threshold for ioctl
frequency,
and the ioctl may return sooner than synchronize RCU, letting the ioctl vCPU
have
a better response.
How do you think? Or do you have any better ideas? Thanks in advance.
Best regards,
-Gonglei
--
To unsubscribe from this list: send the
GFP_KERNEL);
@@ -635,6 +685,11 @@ static void kvm_destroy_vm(struct kvm *k
list_del(&kvm->vm_list);
raw_spin_unlock(&kvm_lock);
kvm_free_irq_routing(kvm);
+
+ kthread_stop(kvm->kthread);
+ if (kvm->to_update_entries)
+ vfree(
some impact of KVM_SET_GSI_ROUTING ioctl. I
wrote another
patch in that mail and want to be examined to see if it is acceptable or has
any problem, thank you.
Best regards,
-Gonglei
--
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/majordomo-info.html
ned_dev_update_msix_mmio maybe occur the issue of
> entry_nr > 256,
> > and the kmod reports the EINVAL error.
> >
> > My patch fix this issue which alloc memory according to the real size of pci
> device config.
> >
> > Any ideas? Thnaks.
> >
> &g
Hi Kevin & Paolo,
Luckily, I reproduced this problem last night. And I got the below log when
SeaBIOS is stuck.
[BTW, the whole SeaBIOS log attached]
[2015-12-18 10:38:10] >>>>>gonglei: enter smp_setup()...
[2015-12-18 10:38:10] >>>>>gonglei: begine to enable
>
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Saturday, December 19, 2015 7:13 AM
> To: Gonglei (Arei)
> Cc: Xulei (Stone); Paolo Bonzini; qemu-devel; seab...@seabios.org;
> Huangweidong (C); kvm@vger.kernel.org
> Subject: Re: [Qemu-devel] [PATCH] Se
Hi Kevin,
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
>
> On Fri, Dec 18, 2015 at 03:04:58AM +, Gonglei (Arei) wrote:
> > Hi Kevin & Paolo,
> >
> > Luckily, I reproduced this problem last night. And I go
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Saturday, December 19, 2015 11:12 PM
> On Sat, Dec 19, 2015 at 12:03:15PM +, Gonglei (Arei) wrote:
> > Maybe the root cause is not NMI but INTR, so yield() can open hardware
&g
Dear Kevin,
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Sunday, December 20, 2015 10:33 PM
> To: Gonglei (Arei)
> Cc: Xulei (Stone); Paolo Bonzini; qemu-devel; seab...@seabios.org;
> Huangweidong (C); kvm@vger.kernel.org; Rad
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Tuesday, December 22, 2015 2:47 AM
> To: Gonglei (Arei)
> Cc: Xulei (Stone); Paolo Bonzini; qemu-devel; seab...@seabios.org;
> Huangweidong (C); kvm@vger.kernel.org; Radim Krcmar
>
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Tuesday, December 22, 2015 11:51 PM
> To: Gonglei (Arei)
> Cc: Xulei (Stone); Paolo Bonzini; qemu-devel; seab...@seabios.org;
> Huangweidong (C); kvm@vger.kernel.org; Radim Krcmar
>
Hi all,
XEN supported last branch recording(LBR) since 2007.
And KVM has supported vPMU, but hasn't support LBR for intel CPUs yet.
May I ask why? Is there any considerations to implement it? Thanks.
PS: I tried to google some reasons about this, but I got nothing. :(
Regards,
-Go
18 matches
Mail list logo
