All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Cc: Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org, jailhouse-dev@googlegroups.com,
	Jay Dolan <jay.dolan@accesio.com>
Subject: Re: [PATCH] serial: 8250_pci: Implement MSI(-X) support
Date: Wed, 4 Sep 2019 09:22:06 +0200	[thread overview]
Message-ID: <20190904072206.GA30185@kroah.com> (raw)
In-Reply-To: <740fc1e7-fb3d-c0c7-c17b-2ea3a8864d89@oth-regensburg.de>

On Fri, Aug 30, 2019 at 12:33:09AM +0200, Ralf Ramsauer wrote:
> *ping* :)
> 
> On 8/12/19 1:21 PM, Ralf Ramsauer wrote:
> > There may be setups, where legacy interrupts are not available. This is
> > the caese, e.g., when Linux runs as guest (aka. non-root cell) of the
> > partitioning hypervisor Jailhouse. There, only MSI(-X) interrupts are
> > available for guests.
> > 
> > But the 8250_pci driver currently only supports legacy ints. So let's
> > enable MSI(-X) interrupts.
> > 
> > Nevertheless, this needs to handled with care: while many 8250 devices
> > actually claim to support MSI(-X) interrupts it should not be enabled be
> > default. I had at least one device in my hands with broken MSI
> > implementation.
> > 
> > So better introduce a whitelist with devices that are known to support
> > MSI(-X) interrupts. I tested all devices mentioned in the patch.
> > 
> > Signed-off-by: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>

Ok, will queue this up, let's see what breaks :)

      reply	other threads:[~2019-09-04  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 11:21 [PATCH] serial: 8250_pci: Implement MSI(-X) support Ralf Ramsauer
2019-08-29 22:33 ` Ralf Ramsauer
2019-09-04  7:22   ` Greg Kroah-Hartman [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=20190904072206.GA30185@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jailhouse-dev@googlegroups.com \
    --cc=jay.dolan@accesio.com \
    --cc=jslaby@suse.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=ralf.ramsauer@oth-regensburg.de \
    /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.