| To: | Linux MIPS List <linux-mips@linux-mips.org> |
|---|---|
| Subject: | some question about mips mtc0/mfc0 usage |
| From: | loody <miloody@gmail.com> |
| Date: | Thu, 28 Jun 2012 01:09:12 +0800 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Xz2cVu7+8RUr4cZbjg3dpukPilF2kxDfJAa/KYUVjO4=; b=MpiNx4O+oX9Cn3jo+rsQL6sszzBVNMKBjQmTK3+QW9+/SKg0ROHY7fyNAzDz6ViQ9y FgnWJ3LHRfRpLGZODxng8wx9LBbqZqsAS6VcQdARGn94/YFc7k1aK/p93RH5aaab3uPj IqxSl0QF7auxV9JuMEJ60UQQhYMepeKS2PHJ//kZIwM5jZQURkEsQnTsqkh29H0AeyJs vRYK5nUWQhzjSEmLYjZS2EPd9mmykgGf/oUuDgScmMR7xLFSL8QEjM81C1pD81CvZ0d8 qLbeAInnMYsR7EVfmG7XTIdD4DWqcceKaTPlBh9CP4cEF8aWN8ne2V8DOLbIRHEa74Fn MxIA== |
| List-archive: | <http://www.linux-mips.org/archives/linux-mips/> |
| List-help: | <mailto:ecartis@linux-mips.org?Subject=help> |
| List-id: | linux-mips <linux-mips.eddie.linux-mips.org> |
| List-owner: | <mailto:ralf@linux-mips.org> |
| List-post: | <mailto:linux-mips@linux-mips.org> |
| List-software: | Ecartis version 1.0.0 |
| List-subscribe: | <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips> |
| List-unsubscribe: | <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips> |
| Sender: | linux-mips-bounce@linux-mips.org |
Hi all:
My mips is 24k core series, and I have some questions when I using mtc0/mfc0.
1. no matter what "spacing" in the execution-hazard or
instruction-hazard, is it enough to use "ehb" and "JALR.HB" once?
2.
below is excerpted from the spec.
producer consumer
hazard on spacing
MTC0 -> Interrupted instruction
Status 2
MTC0 ->Load/Store affected by new state
StatusER 3
MTC0 -> Coprocessor instruction affected by new state StatusCU 4
MTC0 -> Instruction fetch seeing the new value
EntryHiASID 10
Are there any example which can tell me what does
" Interrupted instruction"
"Load/Store affected by new state"
"Coprocessor instruction affected by new state"
" Instruction fetch seeing the new value"
mean?
--
Thanks for your help in advance,
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [PATCH 00/33] Cleanup firmware support across multiple platforms., Hill, Steven |
|---|---|
| Next by Date: | [PATCH v2 3/4] netdev/phy/of: Add more methods for binding PHY devices to drivers., David Daney |
| Previous by Thread: | [PATCH v2,05/33] MIPS: AR7: Cleanup files effected by firmware changes., Steven J. Hill |
| Next by Thread: | [PATCH v2 0/4] netdev/phy: 10G PHY support., David Daney |
| Indexes: | [Date] [Thread] [Top] [All Lists] |