mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danilo Krummrich <danilokrummrich@yahoo.de>
To: miguel.ojeda.sandonis@gmail.com, tglx@linutronix.de,
	x86@kernel.org, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, david@readahead.eu,
	sergio.collado@gmail.com
Cc: davidgow@google.com, hpa@zytor.com, john.m.baublitz@gmail.com,
	linux-kernel@vger.kernel.org, mhiramat@kernel.org,
	mingo@kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] x86/insn_decoder_test: allow longer symbol-names
Date: Mon, 8 Apr 2024 14:51:55 +0200	[thread overview]
Message-ID: <d912f0e0-19d5-4cde-a548-10db94da15a9@yahoo.de> (raw)
In-Reply-To: <CANiq72meap5C9bkj5rNDE=0U5gb5OKwDrrTSrVRwJbkAPWgUsg@mail.gmail.com>

On 2/20/24 18:07, Miguel Ojeda wrote:
> 
> On Fri, Jan 27, 2023 at 11:39 AM David Rheinsberg <david@readahead.eu> wrote:
>>
>> The current workaround is to just disable CONFIG_X86_DECODER_SELFTEST, which I thought is a sad state. I can gladly use `256 + KSYM_NAME_LEN` and add a comment ala "room for insn-encoding and a symbol name". Would that be acceptable? The alternative would be to try to dyn-alloc a buffer and increase it to the actual line-length?
> 
> John independently hit this issue again. Could we fix this? Going for
> the `256 + KSYM_NAME_LEN` sounds good enough for the moment since it
> would be a clear improvement, though I agree this could be cleaned up
> further.

I hit this independently as well. Miguel pointed me on this mail thread
when I sent another fix for this in [1].

> 
> Sergio took the approach David suggested in a related patch [1], but
> perhaps it is best to submit the fix on its own so that it is easier
> to put it in. David, would you be so kind as to submit a v2 with that?
> Hopefully x86 can pick it up, otherwise with an Acked-by I am happy to
> take it too; and then Sergio can submit his patch on top again.

Sergio, David: Do you intend to follow up on this? Otherwise, I can also
pick this up and re-submit.

- Danilo

> 
> Thanks!
> 
> (Cc'ing also Masami who wrote this originally)
> 
> [1] https://lore.kernel.org/rust-for-linux/20231119180145.157455-1-sergio.collado@gmail.com/
> 
> Cheers,
> Miguel

[1] https://lore.kernel.org/rust-for-linux/20240325174924.95899-2-dakr@redhat.com/

  reply	other threads:[~2024-04-08 13:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 11:04 David Rheinsberg
2023-01-25 11:30 ` Ingo Molnar
2023-01-27 10:27   ` David Rheinsberg
2024-02-20 17:07     ` Miguel Ojeda
2024-04-08 12:51       ` Danilo Krummrich [this message]
2024-04-08 15:22         ` Sergio González Collado
2024-04-08 15:30           ` Sergio González Collado
2024-11-29 15:40 Richard W.M. Jones
2024-12-24 15:24 ` Andrew Halaney

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=d912f0e0-19d5-4cde-a548-10db94da15a9@yahoo.de \
    --to=danilokrummrich@yahoo.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@readahead.eu \
    --cc=davidgow@google.com \
    --cc=hpa@zytor.com \
    --cc=john.m.baublitz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sergio.collado@gmail.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®