The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" 
	<linux-ide@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH v2 1/3] ata: ahci: Rename board_ahci_mobile
Date: Fri, 25 Feb 2022 17:16:03 +0100	[thread overview]
Message-ID: <e65c4fbb-95d0-5c5a-2b15-414b519d3319@redhat.com> (raw)
In-Reply-To: <BL1PR12MB5157D29423AE95EE32F00303E23E9@BL1PR12MB5157.namprd12.prod.outlook.com>

Hi,

On 2/25/22 17:04, Limonciello, Mario wrote:
> [Public]
> 
>> On Fri, Feb 25, 2022 at 12:11:11AM -0600, Mario Limonciello wrote:
>>> This board definition was originally created for mobile devices to
>>> designate default link power managmeent policy to influence runtime
>>> power consumption.
>>>
>>> As this is interesting for more than just mobile designs, rename the
>>> board to `board_ahci_low_power` to make it clear it is about default
>>> policy.
>>
>> Is there any good reason to not just apply the policy to all devices
>> by default?
> 
> That sure would make this all cleaner.
> 
> I think Hans knows more of the history here than anyone else.  I had
> presumed there was some data loss scenarios with some of the older
> chipsets.

When I first introduced this change there were reports of crashes and
data corruption caused by setting the policy to min_power, these were
tied to some motherboards and/or to some drives.

This is the whole reason why I only enabled this on a subset of all the
AHCI chipsets.

At least on devices with a chipset which is currently marked as
mobile, the motherboard specific issues could be fixed with a BIOS
update. But I doubt that similar BIOS fixes have also been rolled
out to all desktop boards (and have been applied by all users),
and I also don't know about older boards.

So enabling this on all chipsets is definitely not without risks.

Regards,

Hans




> 
> Hans?
> 


  reply	other threads:[~2022-02-25 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  6:11 [PATCH v2 1/3] ata: ahci: Rename board_ahci_mobile Mario Limonciello
2022-02-25  6:11 ` [PATCH v2 2/3] ata: ahci: Rename `AHCI_HFLAG_IS_MOBILE` Mario Limonciello
2022-02-25  6:11 ` [PATCH v2 3/3] ata: ahci: Rename CONFIG_SATA_LPM_MOBILE_POLICY configuration item Mario Limonciello
2022-02-25  6:33 ` [PATCH v2 1/3] ata: ahci: Rename board_ahci_mobile Damien Le Moal
2022-02-25  9:24 ` Hans de Goede
2022-02-25 16:01 ` Christoph Hellwig
2022-02-25 16:04   ` Limonciello, Mario
2022-02-25 16:16     ` Hans de Goede [this message]
2022-02-25 16:19       ` Limonciello, Mario
2022-02-25 21:07         ` Hans de Goede
2022-02-25 21:13           ` Limonciello, Mario
2022-02-25 21:19             ` Hans de Goede
2022-02-25 16:21       ` Paul Menzel

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=e65c4fbb-95d0-5c5a-2b15-414b519d3319@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hch@infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox