From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: "'Maciej W. Rozycki'" <macro@imgtec.com>,
"'Petar Jovanovic'" <Petar.Jovanovic@imgtec.com>
Cc: "'David Daney'" <ddaney@caviumnetworks.com>,
<linux-mips@linux-mips.org>, <ralf@linux-mips.org>,
<david.daney@cavium.com>
Subject: RE: [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1
Date: Fri, 7 Jul 2017 13:37:31 +0200 [thread overview]
Message-ID: <000b01d2f715$6bb602f0$432208d0$@rt-rk.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1707062139020.3339@tp.orcam.me.uk>
-----Original Message-----
From: Maciej W. Rozycki
> I think we came to the conclusion that the way to move forward is to
> implement Octeon-specific controls where generic R1/R2 ISA ones are now
> (ab)used to get the desired effect. Only once this is in place your
> change can go in.
As I said earlier in the thread, "in the current ToT, I have not seen
where this change would affect apart from show_cpuinfo()"[1]. So, if
someone implements Octeon-specific controls, where this should be used?
I am not aware of the places where Octeon (ab)uses it in the current
kernel code. David says he "cannot recall exactly what the issues
were" [2].
Petar
[1] https://www.linux-mips.org/archives/linux-mips/2017-05/msg00103.html
[2] https://www.linux-mips.org/archives/linux-mips/2017-03/msg00149.html
WARNING: multiple messages have this Message-ID (diff)
From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: "'Maciej W. Rozycki'" <macro@imgtec.com>,
'Petar Jovanovic' <Petar.Jovanovic@imgtec.com>
Cc: 'David Daney' <ddaney@caviumnetworks.com>,
linux-mips@linux-mips.org, ralf@linux-mips.org,
david.daney@cavium.com
Subject: RE: [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1
Date: Fri, 7 Jul 2017 13:37:31 +0200 [thread overview]
Message-ID: <000b01d2f715$6bb602f0$432208d0$@rt-rk.com> (raw)
Message-ID: <20170707113731.6upU_j8R5i13BhTZtfpPyrg6_RQ5nDhvMETZrOY9H-I@z> (raw)
In-Reply-To: <alpine.DEB.2.00.1707062139020.3339@tp.orcam.me.uk>
-----Original Message-----
From: Maciej W. Rozycki
> I think we came to the conclusion that the way to move forward is to
> implement Octeon-specific controls where generic R1/R2 ISA ones are now
> (ab)used to get the desired effect. Only once this is in place your
> change can go in.
As I said earlier in the thread, "in the current ToT, I have not seen
where this change would affect apart from show_cpuinfo()"[1]. So, if
someone implements Octeon-specific controls, where this should be used?
I am not aware of the places where Octeon (ab)uses it in the current
kernel code. David says he "cannot recall exactly what the issues
were" [2].
Petar
[1] https://www.linux-mips.org/archives/linux-mips/2017-05/msg00103.html
[2] https://www.linux-mips.org/archives/linux-mips/2017-03/msg00149.html
next prev parent reply other threads:[~2017-07-07 11:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 17:59 [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1 Petar Jovanovic
2017-04-05 16:01 ` Petar Jovanovic
2017-04-05 16:01 ` Petar Jovanovic
2017-04-25 17:24 ` Petar Jovanovic
2017-05-08 15:25 ` Petar Jovanovic
2017-05-08 15:25 ` Petar Jovanovic
2017-05-15 11:33 ` Petar Jovanovic
2017-05-21 1:37 ` Maciej W. Rozycki
2017-05-22 16:25 ` David Daney
2017-05-22 16:43 ` Petar Jovanovic
2017-05-22 16:43 ` Petar Jovanovic
2017-05-22 17:52 ` Maciej W. Rozycki
2017-06-16 13:26 ` Petar Jovanovic
2017-06-16 13:26 ` Petar Jovanovic
2017-07-06 16:17 ` Petar Jovanovic
2017-07-06 20:47 ` Maciej W. Rozycki
2017-07-07 11:37 ` Petar Jovanovic [this message]
2017-07-07 11:37 ` Petar Jovanovic
2017-07-07 15:04 ` Maciej W. Rozycki
2017-07-07 15:04 ` Maciej W. Rozycki
2017-07-07 16:19 ` David Daney
2017-08-07 16:59 ` Petar Jovanovic
2017-09-14 16:41 ` Petar Jovanovic
2017-09-14 16:41 ` Petar Jovanovic
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='000b01d2f715$6bb602f0$432208d0$@rt-rk.com' \
--to=petar.jovanovic@rt-rk.com \
--cc=Petar.Jovanovic@imgtec.com \
--cc=david.daney@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@imgtec.com \
--cc=ralf@linux-mips.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