All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Clara Kowalsky <clara.kowalsky@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [PATCH v3][Dovetail 6.6] arm64: dovetail: Fix undefinstr/break trap handling
Date: Tue, 31 Oct 2023 13:55:07 +0100	[thread overview]
Message-ID: <87cywvgdba.fsf@xenomai.org> (raw)
In-Reply-To: <dd9a43fbe4d7099c6017f9383550980bfa44a39b.camel@siemens.com>


Florian Bezdeka <florian.bezdeka@siemens.com> writes:

> On Tue, 2023-10-31 at 12:23 +0100, Philippe Gerum wrote:
>> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
>> 
>> > On Tue, 2023-10-31 at 11:46 +0100, Philippe Gerum wrote:
>> > > Ack. I initially thought we could postpone the in-band switch until
>> > > after some of the emulation code paths have been considered (typically
>> > > the MRS stuff), but that would involve convoluted logic for no obvious
>> > > gain, so let's take the straightforward approach instead. The assumption
>> > > here is that issuing an (emulated) MRS read request from a userland
>> > > application should not happen from a time-critical context anyway, so
>> > > doing this in-band should be acceptable. We'll see from complains if its
>> > > not..
>> > > 
>> > > IOW, patch merged to v6.6, thanks.
>> > 
>> > Nice! Thanks!
>> > 
>> > > 
>> > > PS: There are three Dovetail branches to maintain concurrently ATM,
>> > > twice that number when including the EVL trees. So please always mention
>> > > the kernel release any patch sent my way applies to, this may help
>> > > speeding up the process on my end (e.g. this patch conflicts, needs
>> > > manual backport to v5.10, v6.1.y).
>> > 
>> > We had [Dovetail 6.6] in the subject. I thought that should be
>> > sufficient. Seems it's not. How should we make that clear?
>> 
>> No, that's perfect. PEBKAC detected locally.
>
> Happens to the best ;-)
>
> Let us know if we can help backporting. Clara might have a look
> especially at 6.1 - our preferred target right now.
>

That would be great. I would take care of 5.10 then.

-- 
Philippe.

  reply	other threads:[~2023-10-31 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  9:32 [PATCH v3][Dovetail 6.6] arm64: dovetail: Fix undefinstr/break trap handling Clara Kowalsky
2023-10-31 10:46 ` Philippe Gerum
2023-10-31 11:15   ` Florian Bezdeka
2023-10-31 11:23     ` Philippe Gerum
2023-10-31 11:27       ` Florian Bezdeka
2023-10-31 12:55         ` Philippe Gerum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-24  9:14 Clara Kowalsky

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=87cywvgdba.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=clara.kowalsky@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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.