public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Matthew Wilcox <matthew@wil.cx>, Andrew Morton <akpm@osdl.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	lkml <linux-kernel@vger.kernel.org>,
	Rajesh Shah <rajesh.shah@intel.com>
Subject: Re: [PATCH 1/2]MSI(X) save/restore for suspend/resume
Date: Tue, 10 Jan 2006 17:26:25 -0800	[thread overview]
Message-ID: <20060111012625.GA29108@kroah.com> (raw)
In-Reply-To: <1136942240.5750.35.camel@sli10-desk.sh.intel.com>

On Wed, Jan 11, 2006 at 09:17:19AM +0800, Shaohua Li wrote:
> On Tue, 2006-01-10 at 13:28 -0700, Matthew Wilcox wrote:
> > On Thu, Jan 05, 2006 at 08:58:00AM +0800, Shaohua Li wrote:
> > > +	if ((pos = pci_find_capability(dev, PCI_CAP_ID_MSIX)) <= 0 ||
> > > +		dev->no_msi)
> > 
> > No assignments within conditionals, please.
> Ok.
> 
> > 	pos = pci_find_capability(dev, PCI_CAP_ID_MSIX);
> > 	if (pos <= 0 || dev->no_msi)
> > 
> > >  	u32		saved_config_space[16]; /* config space saved at suspend time */
> > > +	void		*saved_cap_space[PCI_CAP_ID_MAX + 1]; /* ext config space saved at suspend time */
> > >  	struct bin_attribute *rom_attr; /* attribute descriptor for sysfs ROM entry */
> > ...
> > >  #define  PCI_CAP_ID_MSIX	0x11	/* MSI-X */
> > > +#define PCI_CAP_ID_MAX		PCI_CAP_ID_MSIX
> > >  #define PCI_CAP_LIST_NEXT	1	/* Next capability in the list */
> > 
> > Rather than taking all this space in the pci_dev structure (even
> > without CONFIG_PM), how about:
> > 
> > struct pci_cap_saved_state {
> > 	struct pci_cap_saved_state *next;
> > 	char cap_nr;
> > 	char data[0];
> > }
> > 
> > and then just add:
> > 
> > 	struct pci_cap_saved_state *saved_cap_space;
> > 
> > to the struct pci_dev?  One pointer, rather than (currently!) 12.
> > That's an 88 byte saving per PCI device on 64-bit machines!
> It's not that big, right? This will make things a little complex. How
> about just define saved_cap_space[] with CONFIG_PM configured? Anyway,
> if you insist on less space, I'm happy to change it.

A pointer to the structure is much nicer, I'd recommend doing it that
way.

thanks,

greg k-h

  reply	other threads:[~2006-01-11  4:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27  2:05 [PATCH 1/2]MSI(X) save/restore for suspend/resume Shaohua Li
2005-12-27  7:55 ` Arjan van de Ven
2005-12-28  1:24   ` Shaohua Li
2005-12-28  8:25     ` Arjan van de Ven
2005-12-28  8:28       ` Shaohua Li
2006-01-04  7:13 ` Andrew Morton
2006-01-05  0:58   ` Shaohua Li
2006-01-10 20:15     ` Greg KH
2006-01-10 20:28     ` Matthew Wilcox
2006-01-11  1:17       ` Shaohua Li
2006-01-11  1:26         ` Greg KH [this message]
2006-01-11  8:18           ` Shaohua Li
2006-01-11 15:20             ` Matthew Wilcox
2006-01-11 15:51             ` Greg KH
2006-01-11 18:39               ` Matthew Wilcox
2006-01-12  2:30               ` Shaohua Li
2006-01-12  2:47                 ` Matthew Wilcox
2006-01-12  3:17                   ` Shaohua Li
2006-01-12  7:12                     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2006-02-08  9:11 Shaohua Li
2006-02-21  5:24 ` Greg KH
2006-02-22  8:13   ` Shaohua Li

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=20060111012625.GA29108@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=rajesh.shah@intel.com \
    --cc=shaohua.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox