mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Huacai Chen <chenhc@lemote.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Introduce cmdline argument writecombine=
Date: Fri, 7 Aug 2020 02:26:03 +0800	[thread overview]
Message-ID: <c81440ec-a46e-06e1-9ee3-ec3bd2826c4e@flygoat.com> (raw)
In-Reply-To: <20200806165212.GA2754@alpha.franken.de>



在 2020/8/7 上午12:52, Thomas Bogendoerfer 写道:
> On Thu, Aug 06, 2020 at 07:56:20PM +0800, Jiaxun Yang wrote:
>> Our current problem is Loongson's writecombine implementation seems buggy.
>> This is our platform issue rather than target hardware issue.
> ok, so simply clear cpu_data[0].writecombine for the fauly parts
@Tiezhu,

I don't know the exact faulty parts, could you please investigate it in 
Loongson?

I can remember a Loongson stuff told me the issue was solved in GS464E but
there are still users complaining about that.

In fact I can't reproduce it in all of my test systems:
3B1500 + RS780E + R5 230
3A3000 + RS780E Laptop
3A4000 + LS7A + RX550
>> And we don't even know which hardware is known to be good. The same graphic
>> card became a different story on different user's hand.
> find out what is broken and add the needed workarounds then.

Well, let's leave this task for Loongson company.
User's community don't have the ability to trace hardware behavior 
precisely.

>> I understood what Teizhu thought. For entry-level users, we don't want to
>> trouble
>> them, so we have writecombine disabled by default. However, for advanced
>> user
>> trying to tweak their system, we should leave a switch for them to get it
>> back.
> IMHO if we do it that way, we end up with millions of knobs for tweaking
> broken hardware, and nobody knows what's exactly broken. Sorry I won't go
> that way.

Haha, that was my first impression to Linux as a primary school student. 
It just
looks like an aircraft cockpit with thousands of knobs & switches, but 
to airborne
you just need to control yoke and throttle.

- Jiaxun

      reply	other threads:[~2020-08-06 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  7:09 Tiezhu Yang
2020-08-06  7:39 ` Jiaxun Yang
2020-08-06  8:32   ` Tiezhu Yang
2020-08-06 10:17     ` Thomas Bogendoerfer
2020-08-06 11:56       ` Jiaxun Yang
2020-08-06 16:52         ` Thomas Bogendoerfer
2020-08-06 18:26           ` Jiaxun Yang [this message]

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=c81440ec-a46e-06e1-9ee3-ec3bd2826c4e@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhc@lemote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=yangtiezhu@loongson.cn \
    /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

all inboxes | Powered by JetHome®