From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Dan Malek" <dan@embeddededge.com>
Cc: "Tom Rini" <trini@kernel.crashing.org>,
"Jean-Denis Boyer" <jdboyer@m5t.com>,
"Steffen Rumler" <Steffen.Rumler@siemens.com>,
"linuxppc" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problem of concurrency in arch/ppc/8260_io/uart.c
Date: Sat, 27 Sep 2003 10:07:54 +0200 [thread overview]
Message-ID: <001701c384ce$7a5c3ae0$020120b0@jockeXP> (raw)
In-Reply-To: 3F74C7D4.4020000@embeddededge.com
> Joakim Tjernlund wrote:
>
> > Yes, thats correct. I did try different ways around that but the only thing that
> > would work is to make copy_from_user() copy to i tmp buf and then copy the
> > tmp buf into the BD. Would that be better?
>
> I wonder what happens if we mark a buffer ready with a count of zero?
> Since the typical case is no page fault, I would just update the BD ptr
> early, use the buffer, mark it ready. If you get a fault, put a zero
> for the count and mark it ready.
I tried that and it broke the CPM.
> If that freaks out the CPM, put one
> byte of zero into the buffer and give it a count of 1. Then you just have
> to hold the lock across the update of the BD ptr, just like everywhere else.
That will work, but wont the zero show up on the console? hmm, since
the zero count will be very unlikely case anyhow, I can live with that.
Jocke
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-27 8:07 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 16:26 Problem of concurrency in arch/ppc/8260_io/uart.c Jean-Denis Boyer
2003-09-15 18:37 ` Joakim Tjernlund
2003-09-15 18:53 ` Dan Malek
2003-09-15 20:02 ` Joakim Tjernlund
2003-09-16 12:25 ` Joakim Tjernlund
2003-09-17 9:33 ` Joakim Tjernlund
2003-09-17 13:38 ` Joakim Tjernlund
2003-09-17 14:58 ` Dan Malek
2003-09-17 15:22 ` Joakim Tjernlund
2003-09-17 16:33 ` Joakim Tjernlund
2003-09-23 8:28 ` Joakim Tjernlund
2003-09-26 16:31 ` Tom Rini
2003-09-26 18:34 ` Joakim Tjernlund
2003-09-26 18:38 ` Tom Rini
2003-09-26 21:24 ` Tom Rini
2003-09-26 22:20 ` Dan Malek
2003-09-26 22:39 ` Joakim Tjernlund
2003-09-26 23:12 ` Dan Malek
2003-09-27 8:07 ` Joakim Tjernlund [this message]
2003-09-27 13:43 ` Joakim Tjernlund
2003-09-29 15:33 ` Tom Rini
2003-09-30 15:28 ` Dan Malek
2003-10-01 14:26 ` Kumar Gala
2003-10-01 14:32 ` Tom Rini
2003-10-01 14:48 ` Gary Thomas
2003-10-01 21:20 ` Joakim Tjernlund
2003-10-01 21:32 ` Tom Rini
2003-10-01 21:51 ` Joakim Tjernlund
2003-10-01 22:00 ` Tom Rini
2003-10-01 22:17 ` Joakim Tjernlund
2003-10-01 22:31 ` Tom Rini
2003-10-01 23:23 ` Robin Gilks
2003-10-01 23:51 ` Tom Rini
2003-10-02 0:47 ` Wolfgang Denk
2003-10-02 6:03 ` Dan Kegel
2003-10-02 19:15 ` Tom Rini
[not found] <3F8E8817.5ACD7ACB@siemens.com>
2003-10-16 14:11 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 10:18 Steffen Rumler
2003-09-15 13:30 ` Joakim Tjernlund
2003-03-07 15:18 Jean-Denis Boyer
2003-03-07 12:52 Dayton, Dean
2003-03-06 21:39 Jean-Denis Boyer
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='001701c384ce$7a5c3ae0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=Steffen.Rumler@siemens.com \
--cc=dan@embeddededge.com \
--cc=jdboyer@m5t.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).