All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH 4/4] x86/MSI-X: cleanup
Date: Fri, 13 Mar 2015 19:56:49 +0000	[thread overview]
Message-ID: <55034101.4070309@citrix.com> (raw)
In-Reply-To: <54FF29FE0200007800068361@mail.emea.novell.com>

On 10/03/15 16:29, Jan Beulich wrote:
> - __pci_enable_msix() now checks that an MSI-X capability was actually
>   found
> - pass "pos" to msix_capability_init() as both callers already know it
>   (and hence there's no need to re-obtain it)
> - call __pci_disable_msi{,x}() directly instead of via
>   pci_disable_msi() from __pci_enable_msi{x,}() state validation paths

"__pci_enable_msi{x,}()'s state validation paths" ?

> - use msix_control_reg() instead of open coding it
> - log message adjustments
> - coding style corrections
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

It occurs to me that for further cleanup, it might be quite useful to
have a concrete sbdf type.

All this code does huge quantities of moving sbdf representations in and
out of a u32, and using 4 parameters instead of 1 to functions will
cause excessive register scheduling issues.  In addition, a custom %p
format identifier would help us move in the direction of consistent
representation (which we are currently a long way from).

~Andrew

  reply	other threads:[~2015-03-13 19:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 16:16 [PATCH 0/4] x86/MSI-X: XSA-120 follow-up Jan Beulich
2015-03-10 16:27 ` [PATCH 1/4] x86/MSI-X: be more careful during teardown Jan Beulich
2015-03-10 21:05   ` Andrew Cooper
2015-03-11  8:22     ` Jan Beulich
2015-03-13 18:10   ` Andrew Cooper
2015-03-16 11:03     ` Jan Beulich
2015-03-10 16:28 ` [PATCH 2/4] x86/MSI-X: access MSI‑X table only after having enabled MSI‑X Jan Beulich
2015-03-13 19:18   ` Andrew Cooper
2015-03-16 11:13     ` Jan Beulich
2015-03-10 16:29 ` [PATCH 3/4] x86/MSI-X: reduce fiddling with control register during restore Jan Beulich
2015-03-13 19:38   ` Andrew Cooper
2015-03-10 16:29 ` [PATCH 4/4] x86/MSI-X: cleanup Jan Beulich
2015-03-13 19:56   ` Andrew Cooper [this message]
2015-03-13 20:16 ` [PATCH 0/4] x86/MSI-X: XSA-120 follow-up Andrew Cooper
2015-03-16 15:38   ` Jan Beulich

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=55034101.4070309@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.