r-V SynIC MSR's
> > * setup Hyper-V SynIC evt/msg pages
> > * setup SINT's routing
> > * inject SINT's into destination vCPU by 'hyperv-synic-test-device'
> > * wait for SINT's isr's completion
> > * clear Hyper-V SynIC evt/msg pages and
On Tue, Nov 03, 2015 at 03:51:16PM +0100, Paolo Bonzini wrote:
>
>
> On 03/11/2015 15:36, Andrey Smetanin wrote:
> >>
> >>
> >> if I run a patched QEMU but I *do not* enable the synthetic interrupt
> >> controller. I can fix it by wrapping the calls to synic_exit with "if
> >> (!host)", but I ha
s of the corresponding configuration
> MSR. If deemed necessary, the "catch up" mode (the timer period is
> shortened until the timer catches up) will be implemented later.
>
> Signed-off-by: Andrey Smetanin
> CC: Gleb Natapov
> CC: Paolo Bonzini
> CC: "K.
and let the message sources compete for the slot again.
>
> Signed-off-by: Andrey Smetanin
> CC: Gleb Natapov
> CC: Paolo Bonzini
> CC: "K. Y. Srinivasan"
> CC: Haiyang Zhang
> CC: Vitaly Kuznetsov
> CC: Roman Kagan
> CC: Denis V. Lunev
> CC: qemu-de...@n
On Fri, Nov 27, 2015 at 11:49:40AM +0100, Paolo Bonzini wrote:
[ sorry missed your message on Friday, replying now ]
> On 27/11/2015 09:12, Roman Kagan wrote:
> >> > +n = div64_u64(time_now - stimer->exp_time, stimer->count) + 1;
> >> > +stim
On Fri, Dec 18, 2015 at 06:19:25PM +0300, Pavel Fedin wrote:
> I dislike implementing architecture-dependent exit code where we could
> implement an architecture-independent one.
>
> As far as i understand this code, KVM_EXIT_HYPERV is called when one of
> three MSRs are accessed. But, shouldn
On Fri, Dec 18, 2015 at 05:01:59PM +0100, Paolo Bonzini wrote:
> On 18/12/2015 16:19, Pavel Fedin wrote:
> > As far as i understand this code, KVM_EXIT_HYPERV is called when one
> > of three MSRs are accessed. But, shouldn't we have implemented
> > instead something more generic, like KVM_EXIT_REG
On Fri, Dec 18, 2015 at 10:10:11AM -0800, Peter Hornyack wrote:
> On Fri, Dec 18, 2015 at 8:01 AM, Paolo Bonzini wrote:
> > On 18/12/2015 16:19, Pavel Fedin wrote:
> >> As far as i understand this code, KVM_EXIT_HYPERV is called when one
> >> of three MSRs are accessed. But, shouldn't we have impl
On Tue, Dec 22, 2015 at 10:24:13AM +0300, Pavel Fedin wrote:
> > +On the return path into kvm, user space should set handled to
> > +KVM_EXIT_MSR_HANDLED if it successfully handled the MSR access. Otherwise,
> > +handled should be set to KVM_EXIT_MSR_UNHANDLED, which will cause a general
> > +prote
On Tue, Dec 22, 2015 at 03:51:52PM +0300, Pavel Fedin wrote:
> Hello!
>
> > > 1. Is there any real need to distinguish between KVM_EXIT_MSR_WRITE and
> > KVM_EXIT_MSR_AFTER_WRITE ? IMHO from userland's point of view these are the
> > same.
> >
> > Indeed. Perhaps the kernel can set .handled to
On Thu, Dec 24, 2015 at 12:30:26PM +0300, Andrey Smetanin wrote:
> Currently on x86 arch we has already 32 requests defined
> so the newer request bits can't be placed inside
> vcpu->requests(unsigned long) inside x86 32 bit system.
> But we are going to add a new request in x86 arch
> for Hyper-V
On Wed, Dec 23, 2015 at 04:53:59PM +0300, Andrey Smetanin wrote:
> Trace the following Hyper SynIC events:
> * set msr
> * set sint irq
> * ack sint
> * sint irq eoi
>
> Signed-off-by: Andrey Smetanin
> CC: Gleb Natapov
> CC: Paolo Bonzini
> CC: Roman Kagan
>
tup
> * timer cleanup
>
> Signed-off-by: Andrey Smetanin
> CC: Gleb Natapov
> CC: Paolo Bonzini
> CC: Roman Kagan
> CC: Denis V. Lunev
> CC: qemu-de...@nongnu.org
> ---
> arch/x86/kvm/hyperv.c | 27 +++-
> arch/x86/kvm/trace.h | 170
> +
: James Hogan
> CC: Paolo Bonzini
> CC: Gleb Natapov
> CC: James Hogan
> CC: Paul Burton
> CC: Ralf Baechle
> CC: Alexander Graf
> CC: Christian Borntraeger
> CC: Cornelia Huck
> CC: linux-m...@linux-mips.org
> CC: kvm-...@vger.kernel.org
> CC: linux-
On Fri, Sep 18, 2015 at 03:55:00PM +0200, Paolo Bonzini wrote:
>
>
> On 18/09/2015 15:51, Denis V. Lunev wrote:
> >> 185
> >> > 186task_cputime_adjusted(current, &utime, &stime);
> >> 187return div_u64(cputime_to_nsecs(utime + stime), 100);
> >> 188}
> >>
On Fri, Oct 16, 2015 at 09:51:58AM +0200, Paolo Bonzini wrote:
> The documentation should include the definition of the struct and the
> definition of the subtypes (currently KVM_EXIT_HYPERV_SYNIC only).
>
> Documentation for KVM_CAP_HYPERV_SINIC and KVM_IRQ_ROUTING_HV_SINT is
> missing, too.
>
>
On Wed, Oct 28, 2015 at 06:41:45PM +0100, Paolo Bonzini wrote:
> Hi Andrey,
>
> just one question. Is kvm_arch_set_irq actually needed? I think
> everything should work fine without it. Can you check? If so, I can
> remove it myself and revert the patch that introduced the hook.
While Andrey
17 matches
Mail list logo
