linux-kernel - Re: [PATCH] libata: Export AHCI capabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 18 Jul 2009 06:02:33 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	jgarzik@...ox.com
Subject: Re: [PATCH] libata: Export AHCI capabilities

On Fri, Jul 17, 2009 at 10:49:15PM -0600, Robert Hancock wrote:

> Surely there's a better format for exporting this information to  
> userspace than making it parse out the bits from the raw register  
> contents.. how about separate sysfs files for ESP, HPCP, etc? Or  
> something more abstracted at a higher level that other drivers (if they  
> have access to similar information) could use?

I could split out more of the information, but there's a balance between 
exposing enough that we won't need to add more values in the near future 
and ending up with one sysfs file for pretty much every capabilities 
bit. I'm not aware of any cases where we can currently generalise this 
to other controllers, but I'm happy to be proven wrong on that.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/