mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Craig-Wood <nick@craig-wood.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: David Wagner <daw@cs.berkeley.edu>, linux-kernel@vger.kernel.org
Subject: Re: Checking module parameters
Date: Mon, 19 Jan 2009 12:44:36 +0000	[thread overview]
Message-ID: <20090119124436.GD1646@craig-wood.com> (raw)
In-Reply-To: <497453B6.8090403@s5r6.in-berlin.de>

On Mon, Jan 19, 2009 at 11:19:34AM +0100, Stefan Richter wrote:
> Nick Craig-Wood wrote:
> > David Wagner <daw@cs.berkeley.edu> wrote:
> >>  Is there a way to tell what options have been applied to a currently
> >>  loaded kernel module?
> >> 
> >>  I'm trying to force libata to use 1.5Gbps rather than 3Gbps,
> ...
> > I had to do this recently (under debian I ended up putting
> > "libata force=1.5Gbps" into /etc/modules)
> > 
> > You can check it is working by looking for something like this in the log
> > 
> > [    2.345058] ata1: FORCE: PHY spd limit set to 1.5Gbps
> > [    2.345058] ata1: SATA max UDMA/133 abar m2048@0xfb106000 port 0xfb106100 irq 218
> 
> There is also /sys/module/*/parameters/* which can be read and in some
> cases even be written.

It doesn't appear to show the force parameter.  From the same server
as above :-

$ more /sys/module/libata/parameters/* | cat
::::::::::::::
/sys/module/libata/parameters/acpi_gtf_filter
::::::::::::::
3
::::::::::::::
/sys/module/libata/parameters/allow_tpm
::::::::::::::
0
::::::::::::::
/sys/module/libata/parameters/ata_probe_timeout
::::::::::::::
7500
::::::::::::::
/sys/module/libata/parameters/atapi_dmadir
::::::::::::::
0
::::::::::::::
/sys/module/libata/parameters/atapi_enabled
::::::::::::::
1
::::::::::::::
/sys/module/libata/parameters/atapi_passthru16
::::::::::::::
1
::::::::::::::
/sys/module/libata/parameters/dma
::::::::::::::
7
::::::::::::::
/sys/module/libata/parameters/fua
::::::::::::::
0
::::::::::::::
/sys/module/libata/parameters/ignore_hpa
::::::::::::::
0
::::::::::::::
/sys/module/libata/parameters/noacpi
::::::::::::::
0

-- 
Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick

  reply	other threads:[~2009-01-19 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bVsVO-15X-19@gated-at.bofh.it>
2009-01-19  9:38 ` Nick Craig-Wood
2009-01-19 10:19   ` Stefan Richter
2009-01-19 12:44     ` Nick Craig-Wood [this message]
2009-01-19 13:06       ` Stefan Richter
2009-01-17 22:26 David Wagner
2009-01-17 23:47 ` Alexey Dobriyan
2009-01-18  0:22 ` Robert Hancock
2009-01-18 15:59 ` Yanko Kaneti
2009-01-18 18:58 ` Alan Cox

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=20090119124436.GD1646@craig-wood.com \
    --to=nick@craig-wood.com \
    --cc=daw@cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.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

all inboxes | Powered by JetHome®