linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Tushar Dave <tdave@nvidia.com>
Cc: 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: Mon, 13 Jan 2025 16:07:49 -0400	[thread overview]
Message-ID: <20250113200749.GW5556@nvidia.com> (raw)
In-Reply-To: <0ea48a2b-0b6d-49e2-b3f7-ab4deef90696@nvidia.com>

On Wed, Jan 08, 2025 at 07:13:34PM -0800, Tushar Dave wrote:
> > Yes, but X in config_acs should copy the FW value not the value
> > modified by disable_acs_redir_param
> 
> I see your point. In that case (for the last hunk in my patch) something
> like this should work IMO.
> 
> -       /* If mask is 0 then we copy the bit from the firmware setting. */
> -       caps->ctrl = (caps->ctrl & ~mask) | (caps->fw_ctrl & mask);
> -       caps->ctrl |= flags;
> +       /* For unchanged ACS bits 'x' or 'X', copy the bits from the
> firmware setting. */
> +        if (!acs_mask)
> +                caps->ctrl = caps->fw_ctrl;
> +
> +       caps->ctrl &= ~mask;
> +       caps->ctrl |= (flags & mask);
> 
> Wish I can have better condition check instead of 'if (!acs_mask)' but let
> me know your thoughts.

It should be per-bit surely? I think the original logic was the right
idea, just the bit logic had the wrong operators..

Jason

  reply	other threads:[~2025-01-13 20:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 20:29 [PATCH 1/1] PCI: Fix Extend ACS configurability 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
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 [this message]
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=20250113200749.GW5556@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --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=tdave@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;
as well as URLs for NNTP newsgroup(s).