All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Paul Burton <paul.burton@imgtec.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, Marcel Apfelbaum <marcel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] msi: remove return code for msi_init()
Date: Fri, 02 Jun 2017 09:47:20 +0200	[thread overview]
Message-ID: <87r2z2kf07.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20170602041857.GA4056@pxdev.xzpeter.org> (Peter Xu's message of "Fri, 2 Jun 2017 12:18:57 +0800")

Peter Xu <peterx@redhat.com> writes:

> On Thu, Jun 01, 2017 at 03:06:29PM -0700, Paul Burton wrote:
>> Hi Aurelien/Paolo/Marcel,
>> 
>> On Thursday, 1 June 2017 12:22:06 PDT Aurelien Jarno wrote:
>> > On 2017-06-01 16:23, Paolo Bonzini wrote:
>> > > On 01/06/2017 10:27, Marcel Apfelbaum wrote:
>> > > > On 31/05/2017 11:28, Paolo Bonzini wrote:
>> > > >> No, for now I'd rather just go and remove msi_nonbroken.  When someone
>> > > >> reports a bug, we can add back "msi_broken".
>> > > > 
>> > > > Hi,
>> > > > I agree with the direction, but I am concerned msi_nonbroken is there
>> > > > for a reason.
>> > > > We might break some (obscure/not in use) machine.
>> > > > Maybe we should CC all arch machine maintainers/contributors to give
>> > > > them a chance to object...
>> > > 
>> > > Yeah, Alpha, MIPS and SH are those that support PCI.  Adding Richard and
>> > > Aurelien, do your platforms support MSI on real hardware but not in QEMU?
>> > 
>> > SH clearly doesn't support MSI.
>> > 
>> > The oldest MIPS board also do not support MSI, but I guess the Boston
>> > board might support it. I am adding Paul Burton in Cc: who probably
>> > knows about that.
>> > 
>> > Aurelien
>> 
>> Indeed, real Boston hardware does support MSI (or rather, the Xilinx AXI 
>> Bridge for PCI Express IP used on Boston does) & we make use of it in Linux.
>> 
>> Thanks,
>>     Paul
>
> Does this mean that we'd better still keep the msi_nonbroken bit?

If we still need the "monkey-patch MSI-capable devices to hide board
bugs" logic, it should become opt-in rather than opt-out, i.e. broken
boards set msi_broken (with a suitable comment), non-broken boards don't
touch it.

> Anyway, maybe we can first merge Paolo's fix on edu device:
>
>   [PATCH] edu: fix memory leak on msi_broken platforms
>
> Then we can see whether we still need the rest of the changes.
>
> Thanks,

      reply	other threads:[~2017-06-02  7:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 13:14 [Qemu-devel] [PATCH] msi: remove return code for msi_init() Peter Xu
2017-05-29  6:08 ` Peter Xu
2017-05-29  9:42   ` Markus Armbruster
2017-05-29 10:13     ` Peter Xu
2017-05-29 12:16       ` Markus Armbruster
2017-05-30  9:16         ` Paolo Bonzini
2017-05-30 14:28           ` Markus Armbruster
2017-05-30 14:29             ` Paolo Bonzini
2017-05-31  7:03               ` Peter Xu
2017-05-31  7:40                 ` Paolo Bonzini
2017-05-31  8:26                   ` Peter Xu
2017-05-31  8:28                     ` Paolo Bonzini
2017-05-31  8:55                       ` Peter Xu
2017-06-01  8:27                       ` Marcel Apfelbaum
2017-06-01 14:23                         ` Paolo Bonzini
2017-06-01 19:22                           ` Aurelien Jarno
2017-06-01 22:06                             ` Paul Burton
2017-06-02  4:18                               ` Peter Xu
2017-06-02  7:47                                 ` Markus Armbruster [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=87r2z2kf07.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=paul.burton@imgtec.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --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 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.