mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Hilber <peter.hilber@opensynergy.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	lakshmi.sowjanya.d@intel.com, jstultz@google.com,
	giometti@enneenne.com, corbet@lwn.net,
	linux-kernel@vger.kernel.org
Cc: x86@kernel.org, linux-doc@vger.kernel.org,
	andriy.shevchenko@linux.intel.com, eddie.dong@intel.com,
	christopher.s.hall@intel.com, pandith.n@intel.com,
	mallikarjunappa.sangannavar@intel.com,
	thejesh.reddy.t.r@intel.com
Subject: Re: [PATCH v1 4/6] pps: generators: Add PPS Generator TIO Driver
Date: Fri, 20 Oct 2023 17:41:49 +0200	[thread overview]
Message-ID: <c032b7f7-ccea-4e3d-a3fc-d772d034b195@opensynergy.com> (raw)
In-Reply-To: <87lec15i4b.ffs@tglx>

On 17.10.23 18:27, Thomas Gleixner wrote:
> On Tue, Oct 17 2023 at 10:54, lakshmi.sowjanya.d@intel.com wrote:
>> +	guard(spinlock_irqsave)(&tio->lock);
>> +	if (enable && !tio->enabled) {
>> +		if (!is_current_clocksource_art_related()) {
>> +			dev_err(tio->dev, "PPS cannot be started as clock is not related to ART");
>> +			return -EPERM;
>> +		}
> 
> Ah. Here is the usecase for this magic patch 3/6 hackery. Again, it's
> the wrong abstraction. You want something like:
> 
>     timekeeping_clocksource_has_base(CSID_X86_ART);
> 
> or something like this, which can be handled completely in the core
> code.
> 
> All of this needs some serious rework. See the below disfunctional
> mockup patch for illustration.
> 
> There is also a patch series, which tried to replace the clocksource
> pointer in system_counterval_t with a clocksource ID:
> 
>   https://lore.kernel.org/all/20230818011256.211078-1-peter.hilber@opensynergy.com
> 
> That went nowhere, but has some valid points. I took some of Peter's (cc'ed)
> ideas into the mockup, but did it slightly different to make all of this
> indirection mess go away.
> 
> There are certainly bugs and thinkos in that mockup. If you find them,
> you can keep and fix them :)
> 

Hi Sowjanya,

I am working on another iteration of the patch series cited by Thomas,
which would implement part of the mockup. But the scope of the original
patch series would remain, so no changes to ART conversion code, no
introduction of the clocksource_base concept... The patch series should
still be compatible with Thomas' proposal, though.

I was wondering if it would make sense to coordinate the posting of my
patch series. I planned to post the series sometime in November along with
other stuff, but I could potentially post it earlier if this could help to
align.

In case of interest in aligning, I uploaded an unverified preview for the
upcoming series to [1].

Best regards,

Peter

[1] https://github.com/OpenSynergy/linux.git clocksource-id-for-get_device_system_crosststamp-v2-preview

  parent reply	other threads:[~2023-10-20 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  5:24 [PATCH v1 0/6] Add support for Intel PPS Generator lakshmi.sowjanya.d
2023-10-17  5:24 ` [PATCH v1 1/6] kernel/time: Add system time to system counter conversion lakshmi.sowjanya.d
2023-10-17  8:42   ` Thomas Gleixner
2023-10-17  5:24 ` [PATCH v1 2/6] x86/tsc: Convert Time Stamp Counter (TSC) value to Always Running Timer (ART) lakshmi.sowjanya.d
2023-10-17  9:29   ` Thomas Gleixner
2023-10-17  5:24 ` [PATCH v1 3/6] x86/tsc: Check if the current clock source is related to ART(Always Running Timer) lakshmi.sowjanya.d
2023-10-17 11:16   ` Thomas Gleixner
2023-10-17  5:24 ` [PATCH v1 4/6] pps: generators: Add PPS Generator TIO Driver lakshmi.sowjanya.d
2023-10-17 16:27   ` Thomas Gleixner
2023-10-17 22:58     ` Thomas Gleixner
2023-10-20 15:41     ` Peter Hilber [this message]
2023-12-01 10:22       ` D, Lakshmi Sowjanya
2023-12-01 11:18         ` Peter Hilber
2023-11-22  8:53     ` D, Lakshmi Sowjanya
2023-10-17  5:24 ` [PATCH v1 5/6] Documentation: driver-api: pps: Add Intel Timed I/O PPS generator lakshmi.sowjanya.d
2023-10-17  5:24 ` [PATCH v1 6/6] ABI: pps: Add ABI documentation for Intel TIO lakshmi.sowjanya.d

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=c032b7f7-ccea-4e3d-a3fc-d772d034b195@opensynergy.com \
    --to=peter.hilber@opensynergy.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=christopher.s.hall@intel.com \
    --cc=corbet@lwn.net \
    --cc=eddie.dong@intel.com \
    --cc=giometti@enneenne.com \
    --cc=jstultz@google.com \
    --cc=lakshmi.sowjanya.d@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mallikarjunappa.sangannavar@intel.com \
    --cc=pandith.n@intel.com \
    --cc=tglx@linutronix.de \
    --cc=thejesh.reddy.t.r@intel.com \
    --cc=x86@kernel.org \
    /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

Powered by JetHome