All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	platform-driver-x86@vger.kernel.org, david.e.box@linux.intel.com,
	ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
	rodrigo.vivi@intel.com, lucas.demarchi@intel.com
Subject: Re: [PATCH v2 1/2] platform/x86/intel/pmt: allow user offset for PMT callbacks
Date: Wed, 13 Nov 2024 12:26:07 +0200	[thread overview]
Message-ID: <ZzR-v4wiKCqRcd6q@smile.fi.intel.com> (raw)
In-Reply-To: <20241112163035.2282499-2-michael.j.ruhl@intel.com>

On Tue, Nov 12, 2024 at 11:30:34AM -0500, Michael J. Ruhl wrote:
> Usage of the telem sysfs file allows for partial reads at
> an offset.
> 
> The current callback method returns the buffer starting
> from offset 0 only.
> 
> Include the requested offset in the callback.
> Update the necessary address calculations with the offset.
> 
> Note: offset addition is moved from the caller to the local
> usage.  For non-callback usage this unchanged behavior.

...

>  int pmt_telem_read_mmio(struct pci_dev *pdev, struct pmt_callbacks *cb, u32 guid, void *buf,
> -			void __iomem *addr, u32 count)
> +			void __iomem *addr, loff_t off, u32 count)
>  {
>  	if (cb && cb->read_telem)
> -		return cb->read_telem(pdev, guid, buf, count);
> +		return cb->read_telem(pdev, guid, buf, off, count);

Also possible instead of the below changes is to add here

	addr += off;

>  	if (guid == GUID_SPR_PUNIT)
>  		/* PUNIT on SPR only supports aligned 64-bit read */
> -		return pmt_memcpy64_fromio(buf, addr, count);
> +		return pmt_memcpy64_fromio(buf, addr + off, count);
>  
> -	memcpy_fromio(buf, addr, count);
> +	memcpy_fromio(buf, addr + off, count);
>  
>  	return count;
>  }

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-11-13 10:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 16:30 [PATCH v2 0/2] Support BMG PMT features for Xe Michael J. Ruhl
2024-11-12 16:30 ` [PATCH v2 1/2] platform/x86/intel/pmt: allow user offset for PMT callbacks Michael J. Ruhl
2024-11-13 10:26   ` Andy Shevchenko [this message]
2024-11-13 21:57     ` Ruhl, Michael J
2024-11-12 16:30 ` [PATCH v2 2/2] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-11-13  7:55 ` ✓ CI.Patch_applied: success for Support BMG PMT features for Xe Patchwork
2024-11-13  7:55 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-13  7:56 ` ✓ CI.KUnit: success " Patchwork
2024-11-13  8:08 ` ✓ CI.Build: " Patchwork
2024-11-13  8:10 ` ✓ CI.Hooks: " Patchwork
2024-11-13  8:11 ` ✓ CI.checksparse: " Patchwork
2024-11-13  8:29 ` ✓ CI.BAT: " Patchwork
2024-11-13 10:06 ` ✗ CI.FULL: failure " Patchwork
2024-11-13 10:18 ` [PATCH v2 0/2] " Andy Shevchenko
2024-11-13 10:38 ` Andy Shevchenko
2024-11-13 13:52   ` Ilpo Järvinen
2024-11-13 17:55     ` Andy Shevchenko
2024-11-13 18:40     ` David E. Box
2024-11-13 18:59       ` Andy Shevchenko
2024-11-13 21:00         ` David E. Box
2024-11-13 18:21   ` Ruhl, Michael J

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=ZzR-v4wiKCqRcd6q@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.