All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dmitry Rockosov <rockosov@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: VLAPIC and Event channel relationship or how to map PIRQ to HVM guest
Date: Fri, 3 Mar 2017 10:28:25 -0500	[thread overview]
Message-ID: <20170303152825.GA15263@char.us.ORACLE.com> (raw)
In-Reply-To: <20170303152749.GD14963@char.us.oracle.com>

On Fri, Mar 03, 2017 at 10:27:49AM -0500, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 02, 2017 at 09:11:03PM +0300, Dmitry Rockosov wrote:
> > Konrad,
> > 
> > Thank you for great help!
> > 
> > I will try xen_nopv, looks like it's what I need.
> > But I have one question about below lines of your patch to Linux kernel.
> > 
> > Does it mean, Intel X2APIC virtualization (SDM Vol.3, 29.5) will not work
> > with xen_nopv?
> 
> Nope. It will use x2APIC and LAPIC.

And adding xen-devel back to it.

Please do not drop xen-devel from the emails.
> > 
> >  bool xen_hvm_need_lapic(void)
> >  {+	if (xen_nopv)+		return false;
> > 
> > 
> > Best Regards,
> > Rockosov Dmitry
> > 
> > 2017-03-01 23:32 GMT+03:00 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> > 
> > > On Wed, Feb 22, 2017 at 12:41:16PM +0300, Dmitry Rockosov wrote:
> > > > Hello guys,
> > > >
> > > > Could someone help me with VLAPIC and Event channel relationship? I can't
> > > > find any good design overview for it.
> > >
> > > LAPIC is extensively described in the Intel SDM.
> > >
> > > The event channels are described in the header files, but
> > > also this https://xenbits.xenproject.org/people/dvrabel/event-
> > > channels-F.pdf
> > > may help.
> > >
> > > > Are they compatible things or not?
> > >
> > > They are not.
> > > >
> > > > Actually I want to map any PIRQ to HVM guest (for example keyboard), and
> > > > use VLAPIC to deliver virtual interrupt to HVM guest.
> > >
> > > OK, that should be OK. The problem is that Linux guests will
> > > be default use the event channel vector (243) and ignore the
> > > LAPIC machinery.
> > >
> > > > But seems like all interrupts from keyboard are working through the Event
> > > > Channel Upcall Interrupt with vector 243.
> > >
> > > If you boot with 'xen_nopv' it should use the normal APIC machinery.
> > >
> > > >
> > > > Please, help me or point any useful documentation.
> > > >
> > > > Thank you!
> > > >
> > > > Best Regards,
> > > > Rockosov Dmitry
> > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@lists.xen.org
> > > > https://lists.xen.org/xen-devel
> > >
> > >

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      parent reply	other threads:[~2017-03-03 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  9:41 VLAPIC and Event channel relationship or how to map PIRQ to HVM guest Dmitry Rockosov
2017-03-01 20:32 ` Konrad Rzeszutek Wilk
     [not found]   ` <CAKkXUypDB+0Pd3=9zvgLWtryih3=TxEB0=tEc8dow0vVtjSNfw@mail.gmail.com>
     [not found]     ` <20170303152749.GD14963@char.us.oracle.com>
2017-03-03 15:28       ` Konrad Rzeszutek Wilk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170303152825.GA15263@char.us.ORACLE.com \
    --to=konrad.wilk@oracle.com \
    --cc=rockosov@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.