qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <rth@twiddle.net>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio: Notice when the system doesn't support MSIx at all
Date: Mon, 26 Oct 2015 09:44:47 +0000	[thread overview]
Message-ID: <562DF60F.10509@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA-VsQSk9Jt5-G_c5Sd8z+f5t3i+rjheLnNWLWOE48E=NQ@mail.gmail.com>

On 27/09/15 15:40, Peter Maydell wrote:

> Ping^2 -- this is still confusing users, cf bug LP:1500175.
> 
> thanks
> -- PMM
> 
> On 6 July 2015 at 11:38, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 3 July 2015 at 09:22, Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> wrote:
>>> On 19/05/15 21:29, Richard Henderson wrote:
>>>
>>>> And do not issue an error_report in that case.
>>>>
>>>> Signed-off-by: Richard Henderson <rth@twiddle.net>
>>>> ---
>>>>  hw/virtio/virtio-pci.c | 15 ++++++++++-----
>>>>  1 file changed, 10 insertions(+), 5 deletions(-)
>>>> --
>>>>
>>>> This seems to be about the only sane way to test the value of
>>>> msi_supported from here.  Thoughts?
>>
>>> Ping? Any chance of getting this applied for 2.4 since it's something
>>> that I do get emails about for SPARC64?
>>
>> Michael would like a respin with the commit message correction
>> he suggested. RTH -- could you send out a fixed up version, please?
>>
>> thanks
>> -- PMM

Another ping on this patch - please can we have it for 2.5? It has been
around since before 2.4 and I'd hate for it to miss another release :(


ATB,

Mark.

  reply	other threads:[~2015-10-26  9:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 15:54 [Qemu-devel] virtio-pci msix error Richard Henderson
2015-05-19 19:16 ` Michael S. Tsirkin
2015-05-19 20:11   ` Peter Maydell
2015-05-19 20:29     ` [Qemu-devel] [PATCH] virtio: Notice when the system doesn't support MSIx at all Richard Henderson
2015-05-20  9:59       ` Michael S. Tsirkin
2015-05-20 15:10         ` Richard Henderson
2015-05-21 18:51           ` Mark Cave-Ayland
2015-07-03  8:22       ` Mark Cave-Ayland
2015-07-06 10:38         ` Peter Maydell
2015-09-27 14:40           ` Peter Maydell
2015-10-26  9:44             ` Mark Cave-Ayland [this message]
2015-10-26 10:03               ` Michael S. Tsirkin
2015-10-26 10:09                 ` Mark Cave-Ayland
2015-10-26 10:14                   ` Peter Maydell
2015-10-26 10:29                     ` Michael S. Tsirkin
2015-10-26 10:47                     ` Mark Cave-Ayland
2015-10-26 11:08                       ` Michael S. Tsirkin
2015-05-20  9:58     ` [Qemu-devel] virtio-pci msix error Michael S. Tsirkin
2015-05-20 10:41       ` Peter Maydell
2015-05-20 11:55         ` Fam Zheng
2015-05-20 12:10           ` Peter Maydell
2015-06-13 15:06             ` Mark Cave-Ayland
2015-07-03  8:13               ` Mark Cave-Ayland
2015-07-03  8:16                 ` Peter Maydell
2015-07-03  8:19                   ` Mark Cave-Ayland

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=562DF60F.10509@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).