public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rao, Goutham" <goutham.rao@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] SMP TLB flushes
Date: Thu, 31 Aug 2000 19:04:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205431@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205428@msgid-missing>

Hi,
ptc.g gets RID from bits 63:61 of the address used in the purge instruction.

Thanks
Goutham

-----Original Message-----
From: Manfred Spraul [mailto:manfred@colorfullife.com]
Sent: Thursday, August 31, 2000 10:57 AM
To: linux-ia64@linuxia64.org
Subject: [Linux-ia64] SMP TLB flushes


Is it correct that the SMP part of the SMP flushing code is still
missing? I'm just noisy and I don't understand yet how the ia64 cpu is
supposed to perform tlb flushes.

* ptc.g only gets the address and the size as parameters, but not a
region id. What if cpu 1 (running kswapd, arbitrary thread context)
wants to flush a page from another thread, and that thread is running on
cpu 2?

* could you add a big warning to start_lazy_tlb [kernel/exit.c] that the
function is unsafe?
Both ppc and ia64 scan the task list and assume that they can find each
mm_struct. If someone actually uses start_lazy_tlb, then that would be
incorrect.

Btw, the i386 tlb flush contained a single instruction race (read x,
write y instead of write y, read x) and this was enough for corruptions
- I overlooked one problem with concurrent tlb flushes and thread
switches.

Please cc me, I'm not subscribed to the list.

--
	Manfred

_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64



  parent reply	other threads:[~2000-08-31 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-31 17:57 [Linux-ia64] SMP TLB flushes Manfred Spraul
2000-08-31 18:40 ` Stephan.Zeisset
2000-08-31 18:56 ` David Mosberger
2000-08-31 19:04 ` Rao, Goutham [this message]
2000-08-31 22:28 ` Manfred Spraul

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=marc-linux-ia64-105590678205431@msgid-missing \
    --to=goutham.rao@intel.com \
    --cc=linux-ia64@vger.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