mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tushar Dave <tdave@nvidia.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	corbet@lwn.net, bhelgaas@google.com, paulmck@kernel.org,
	akpm@linux-foundation.org, thuth@redhat.com, rostedt@goodmis.org,
	xiongwei.song@windriver.com, vidyas@nvidia.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, vsethi@nvidia.com,
	sdonthineni@nvidia.com
Subject: Re: [PATCH 1/1] PCI: Fix Extend ACS configurability
Date: Tue, 7 Jan 2025 18:34:35 -0800	[thread overview]
Message-ID: <c7b7316c-127a-4c10-8e94-bcdefd2188d4@nvidia.com> (raw)
In-Reply-To: <20250106205326.GA132024@bhelgaas>



On 1/6/25 12:53, Bjorn Helgaas wrote:
> On Mon, Jan 06, 2025 at 12:34:00PM -0800, Tushar Dave wrote:
>> On 1/2/25 10:40, Jason Gunthorpe wrote:
>>> On Fri, Dec 13, 2024 at 12:29:42PM -0800, Tushar Dave wrote:
>>>
>>>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>>>> index dc663c0ca670..fc1c37910d1c 100644
>>>> --- a/Documentation/admin-guide/kernel-parameters.txt
>>>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>>>> @@ -4654,11 +4654,10 @@
>>>>    				Format:
>>>>    				<ACS flags>@<pci_dev>[; ...]
>>>>    				Specify one or more PCI devices (in the format
>>>> -				specified above) optionally prepended with flags
>>>> -				and separated by semicolons. The respective
>>>> -				capabilities will be enabled, disabled or
>>>> -				unchanged based on what is specified in
>>>> -				flags.
>>>> +				specified above) prepended with flags and separated
>>>> +				by semicolons. The respective capabilities will be
>>>> +				enabled, disabled or unchanged based on what is
>>>> +				specified in flags.
>>>>    				ACS Flags is defined as follows:
>>>>    				  bit-0 : ACS Source Validation
>>>> @@ -4673,7 +4672,7 @@
>>>>    				  '1' – force enabled
>>>>    				  'x' – unchanged
>>>>    				For example,
>>>> -				  pci=config_acs=10x
>>>> +				  pci=config_acs=10x@pci:0:0
>>>>    				would configure all devices that support
>>>>    				ACS to enable P2P Request Redirect, disable
>>>>    				Translation Blocking, and leave Source
>>>
>>> Is this an unrelated change? The format of the command line shouldn't
>>> be changed to fix the described bug, why is the documentation changed?
>>
>> The documentation as it is (i.e. without my patch), is not correct.
>>
>> IOW, config_acs parameter does require flags and it is not optional. Without
>> flags it results into "ACS Flags missing". Therefore I remove word
>> "optionally" from the documentation text.
>>
>> Secondly, the syntax in the example 'pci=config_acs=10x' is incorrect. The
>> correct syntax should be 'pci=config_acs=10x@pci:0:0' that would configure
>> all devices that support ACS to enable P2P Request Redirect, disable
>> Translation Blocking, and leave Source Validation unchanged from whatever
>> power-up or firmware set it to.
> 
> I'd suggest a separate patch to fix the documentation so we don't try
> to relate the doc changes with the code changes.

Sure thing. I will send a separate patch for the doc changes.

-Tushar

  reply	other threads:[~2025-01-08  2:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 20:29 Tushar Dave
2024-12-14 12:30 ` Vidya Sagar
2025-01-02 18:40 ` Jason Gunthorpe
2025-01-06 20:34   ` Tushar Dave
2025-01-06 20:53     ` Bjorn Helgaas
2025-01-08  2:34       ` Tushar Dave [this message]
2025-01-07  0:10     ` Jason Gunthorpe
2025-01-08  2:32       ` Tushar Dave
2025-01-08 15:10         ` Jason Gunthorpe
2025-01-09  3:13           ` Tushar Dave
2025-01-13 20:07             ` Jason Gunthorpe
2025-01-16  3:11               ` Tushar Dave
2025-01-16 19:01                 ` Jason Gunthorpe
2025-01-17  1:21                   ` Tushar Dave
2025-01-17 13:28                     ` Jason Gunthorpe
2025-01-17 18:41                       ` Tushar Dave
2025-01-02 23:26 ` Bjorn Helgaas
2025-01-06 20:45   ` Tushar Dave

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=c7b7316c-127a-4c10-8e94-bcdefd2188d4@nvidia.com \
    --to=tdave@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=helgaas@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sdonthineni@nvidia.com \
    --cc=thuth@redhat.com \
    --cc=vidyas@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=xiongwei.song@windriver.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

all inboxes | Powered by JetHome®