All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Vagin <avagin@gmail.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dmitry Safonov <dima@arista.com>
Subject: Re: [PATCH v2 0/6] arm64: add the time namespace support
Date: Wed, 15 Apr 2020 09:14:43 -0700	[thread overview]
Message-ID: <CANaxB-w+_4BUOYb-5+w1xBPoZGOzBh-LYOFCY-WSysgbAAcn_w@mail.gmail.com> (raw)
In-Reply-To: <1d9c4c56-af16-e54f-08ca-76c6570b2d53@arm.com>

On Tue, Apr 14, 2020 at 2:02 AM Vincenzo Frascino
<vincenzo.frascino@arm.com> wrote:
>
> Hi Andrei,
>
> On 4/11/20 8:33 AM, Andrei Vagin wrote:
> > On Thu, Apr 9, 2020 at 6:23 AM Vincenzo Frascino
> > <vincenzo.frascino@arm.com> wrote:
> >>
> >> I have though a question on something I encountered during the testing of the
> >> patches: I noticed that all the tests related to CLOCK_BOOTTIME_ALARM fail on
> >> arm64 (please find the results below the scissors). Is this expected?
> >
> > static int alarm_clock_get_timespec(clockid_t which_clock, struct
> > timespec64 *tp)
> > {
> >         struct alarm_base *base = &alarm_bases[clock2alarm(which_clock)];
> >
> >         if (!alarmtimer_get_rtcdev())
> >                 return -EINVAL;
> >
> > It is probably that you get EINVAL from here ^^^. I will send a
> > separate patch to handle this case in tests properly.
> >
>
> This makes sense :) Please let me know when you post the fix so I can test it again.

I have sent this fix: https://lkml.org/lkml/2020/4/15/72

>
> Are you planning as well to rebase this set?

What is the right tree to rebase on?

Thanks,
Andrei

WARNING: multiple messages have this Message-ID (diff)
From: Andrei Vagin <avagin@gmail.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Dmitry Safonov <dima@arista.com>
Subject: Re: [PATCH v2 0/6] arm64: add the time namespace support
Date: Wed, 15 Apr 2020 09:14:43 -0700	[thread overview]
Message-ID: <CANaxB-w+_4BUOYb-5+w1xBPoZGOzBh-LYOFCY-WSysgbAAcn_w@mail.gmail.com> (raw)
In-Reply-To: <1d9c4c56-af16-e54f-08ca-76c6570b2d53@arm.com>

On Tue, Apr 14, 2020 at 2:02 AM Vincenzo Frascino
<vincenzo.frascino@arm.com> wrote:
>
> Hi Andrei,
>
> On 4/11/20 8:33 AM, Andrei Vagin wrote:
> > On Thu, Apr 9, 2020 at 6:23 AM Vincenzo Frascino
> > <vincenzo.frascino@arm.com> wrote:
> >>
> >> I have though a question on something I encountered during the testing of the
> >> patches: I noticed that all the tests related to CLOCK_BOOTTIME_ALARM fail on
> >> arm64 (please find the results below the scissors). Is this expected?
> >
> > static int alarm_clock_get_timespec(clockid_t which_clock, struct
> > timespec64 *tp)
> > {
> >         struct alarm_base *base = &alarm_bases[clock2alarm(which_clock)];
> >
> >         if (!alarmtimer_get_rtcdev())
> >                 return -EINVAL;
> >
> > It is probably that you get EINVAL from here ^^^. I will send a
> > separate patch to handle this case in tests properly.
> >
>
> This makes sense :) Please let me know when you post the fix so I can test it again.

I have sent this fix: https://lkml.org/lkml/2020/4/15/72

>
> Are you planning as well to rebase this set?

What is the right tree to rebase on?

Thanks,
Andrei

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-04-15 16:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  7:37 [PATCH v2 0/6] arm64: add the time namespace support Andrei Vagin
2020-02-25  7:37 ` Andrei Vagin
2020-02-25  7:37 ` [PATCH v2 1/6] arm64/vdso: use the fault callback to map vvar pages Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:01   ` Vincenzo Frascino
2020-04-09 12:01     ` Vincenzo Frascino
2020-02-25  7:37 ` [PATCH v2 2/6] arm64/vdso: Zap vvar pages when switching to a time namespace Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:01   ` Vincenzo Frascino
2020-04-09 12:01     ` Vincenzo Frascino
2020-02-25  7:37 ` [PATCH v2 3/6] arm64/vdso: Add time napespace page Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:03   ` Vincenzo Frascino
2020-04-09 12:03     ` Vincenzo Frascino
2020-04-14 17:20   ` Mark Rutland
2020-04-14 17:20     ` Mark Rutland
2020-04-15  2:34     ` Andrei Vagin
2020-04-15  2:34       ` Andrei Vagin
2020-04-15 10:05       ` Mark Rutland
2020-04-15 10:05         ` Mark Rutland
2020-04-15 10:16         ` Vincenzo Frascino
2020-04-15 10:16           ` Vincenzo Frascino
2020-04-15 12:27           ` Mark Rutland
2020-04-15 12:27             ` Mark Rutland
2020-02-25  7:37 ` [PATCH v2 4/6] arm64/vdso: Handle faults on timens page Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:04   ` Vincenzo Frascino
2020-04-09 12:04     ` Vincenzo Frascino
2020-02-25  7:37 ` [PATCH v2 5/6] arm64/vdso: Restrict splitting VVAR VMA Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:05   ` Vincenzo Frascino
2020-04-09 12:05     ` Vincenzo Frascino
2020-02-25  7:37 ` [PATCH v2 6/6] arm64: enable time namespace support Andrei Vagin
2020-02-25  7:37   ` Andrei Vagin
2020-04-09 12:06   ` Vincenzo Frascino
2020-04-09 12:06     ` Vincenzo Frascino
2020-04-01  6:50 ` [PATCH v2 0/6] arm64: add the " Andrei Vagin
2020-04-01  6:50   ` Andrei Vagin
2020-04-01  9:02   ` Vincenzo Frascino
2020-04-01  9:02     ` Vincenzo Frascino
2020-04-09 13:24 ` Vincenzo Frascino
2020-04-09 13:24   ` Vincenzo Frascino
2020-04-11  7:33   ` Andrei Vagin
2020-04-11  7:33     ` Andrei Vagin
2020-04-14  9:02     ` Vincenzo Frascino
2020-04-14  9:02       ` Vincenzo Frascino
2020-04-15 16:14       ` Andrei Vagin [this message]
2020-04-15 16:14         ` Andrei Vagin
2020-04-15 16:35         ` Vincenzo Frascino
2020-04-15 16:35           ` Vincenzo Frascino

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=CANaxB-w+_4BUOYb-5+w1xBPoZGOzBh-LYOFCY-WSysgbAAcn_w@mail.gmail.com \
    --to=avagin@gmail.com \
    --cc=dima@arista.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.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.