From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH v4 15/16] driver/edac: enable Hygon support to AMD64 EDAC driver Date: Tue, 21 Aug 2018 13:20:20 +0200 Message-ID: <20180821112020.GB29972@nazgul.tnic> References: <6275a5a0a0cfbd2c1abc09a5bb41caabecd02e27.1534599097.git.puwen@hygon.cn> <20180821081331.GC24940@nazgul.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Pu Wen Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, thomas.lendacky@amd.com, pbonzini@redhat.com, mchehab@kernel.org, mikhail.jin@gmail.com, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-edac@vger.kernel.org List-Id: linux-arch.vger.kernel.org On Tue, Aug 21, 2018 at 07:04:23PM +0800, Pu Wen wrote: > Sure, JV will negotiate with AMD and make sure only JV use family 18h and > AMD won't use family 0x18h, which will make the patch tight and clear. > > What's the best way to adapt for EDAC driver? > * To simplify the code based on AMD won't do family 0x18 and remove > vendor checking. That, provided AMD won't use family 0x18. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.skyhub.de ([5.9.137.197]:44398 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726798AbeHUOkR (ORCPT ); Tue, 21 Aug 2018 10:40:17 -0400 Date: Tue, 21 Aug 2018 13:20:20 +0200 From: Borislav Petkov Subject: Re: [PATCH v4 15/16] driver/edac: enable Hygon support to AMD64 EDAC driver Message-ID: <20180821112020.GB29972@nazgul.tnic> References: <6275a5a0a0cfbd2c1abc09a5bb41caabecd02e27.1534599097.git.puwen@hygon.cn> <20180821081331.GC24940@nazgul.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Pu Wen Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, thomas.lendacky@amd.com, pbonzini@redhat.com, mchehab@kernel.org, mikhail.jin@gmail.com, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-edac@vger.kernel.org Message-ID: <20180821112020.qY5yx06VqLW_FWugJGVrUGaHCg5xxWwYv8LYUfkj7n4@z> On Tue, Aug 21, 2018 at 07:04:23PM +0800, Pu Wen wrote: > Sure, JV will negotiate with AMD and make sure only JV use family 18h and > AMD won't use family 0x18h, which will make the patch tight and clear. > > What's the best way to adapt for EDAC driver? > * To simplify the code based on AMD won't do family 0x18 and remove > vendor checking. That, provided AMD won't use family 0x18. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --