linux-um archives
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	linux-um@lists.infradead.org
Cc: richard@nod.at
Subject: Re: [PATCH] um: "borrow" cmpxchg from x86 tree in UML
Date: Fri, 13 Nov 2020 16:58:59 +0100	[thread overview]
Message-ID: <934d3df1539e43b7cc4e7fa2a22d806215ed5b8c.camel@sipsolutions.net> (raw)
In-Reply-To: <e22c7628-29a7-6dea-1707-948f89334a79@cambridgegreys.com>

On Fri, 2020-11-13 at 13:48 +0000, Anton Ivanov wrote:
> 
> I think that was it. Or to be more exact, I hope that was it.
> 
> I went a few times through asm-generic and that looks like all the
> bits which are worth implementing for a uniprocessor architecture as a
> replacement for their generic equivalents.

It seems that word-at-a-time.h with CONFIG_DCACHE_WORD_ACCESS might 
be worthwhile as well?

Also perhaps bug.h; there are a lot of BUG_ON/WARN_ON and similar
things, and especially the _ONCE part looks better there?

ftrace is probably not worth the effort ...

johannes


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


  reply	other threads:[~2020-11-13 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 11:54 [PATCH] um: "borrow" cmpxchg from x86 tree in UML anton.ivanov
2020-11-13 13:48 ` Anton Ivanov
2020-11-13 15:58   ` Johannes Berg [this message]
2020-11-13 17:50     ` Anton Ivanov
2020-11-13 20:21       ` Johannes Berg
2020-11-13 21:41         ` Anton Ivanov
2020-11-16 14:41     ` Anton Ivanov

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=934d3df1539e43b7cc4e7fa2a22d806215ed5b8c.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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