Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp5454787imm; Tue, 16 Oct 2018 10:28:18 -0700 (PDT) X-Google-Smtp-Source: ACcGV61m0uIQHzzLUcrOPOhV91JM/715JNN315VkTAfiPT3/jbpuGKHUmTKg6uBJBD2/P3Q243sA X-Received: by 2002:a63:eb07:: with SMTP id t7-v6mr20854618pgh.441.1539710898785; Tue, 16 Oct 2018 10:28:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539710898; cv=none; d=google.com; s=arc-20160816; b=x8ryB5u56SuxLnEWIuTK7i51bn9nn/Irj/iTb8xJuZpZrZq2EDYlZKU4zTzhP6HLsv npHYwrP4StnWZIfwYnLrgw/3f2s87scMGbJ4bn8rox5GjL/VIjqjK4u2kiiJfuSV1XEY 4Y64DP8ZAIFrtAuHbZ2uALzr5/FhcIfxjCK81wgFfiTCiW+b1THZWzRZ1ShwWHjgakEN 2MNzAui0lmr3rW/dOioP8G4CFbAh8Sw9KjnvhnffoEhP2fQOvv6CF9/JCmBB33cMQcw1 N7Eav+fVEBxNta31absrFpwjwYkS1tWYryDpFTjjNX0T5WEBH3msWY7Tqi61QHyFTgQL xkmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:references:message-id:date :thread-index:thread-topic:subject:cc:to:from:dkim-signature; bh=xs1oKAmQZKMnbyQZIWLwz4nucbWh/FytIoNc2quLmoI=; b=pLurLgQcz16RTkwkxwYoaKZt7UBwniyj9MbNsBIdRDLJfnibhDWP8tgL5ASUvlWxJ5 8f17u3g0XP9xDV6gA8VBvCNxHvXhPoUbHmYBRiI9YzumiNbiAV4k94+7Mq876WOVMB44 RvriEwoa9wUTvUZt/bewMezD+Vef60jNZk08kskfipYPI4BE7kUXT9Rh/MrfZAd8tY+t wVtbjOKDXfobIQIJVdyKsw7u+ob9z1OYOBHHqpoc9jKqq2OBeROqQvVSkH6+9w02ZBTj a+lUXyCCrbG0iMmy1bZJX+a247+SVJhDxOWdEyiFzrtUMTeILtgj/NH178+ClddIPo6t 4RXg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=NrX4xRKi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p6-v6si14725225pgp.243.2018.10.16.10.28.02; Tue, 16 Oct 2018 10:28:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=NrX4xRKi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727297AbeJQBTC (ORCPT + 99 others); Tue, 16 Oct 2018 21:19:02 -0400 Received: from smtprelay.synopsys.com ([198.182.47.9]:45956 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727213AbeJQBTB (ORCPT ); Tue, 16 Oct 2018 21:19:01 -0400 Received: from mailhost.synopsys.com (mailhost3.synopsys.com [10.12.238.238]) by smtprelay.synopsys.com (Postfix) with ESMTP id 0181124E0D73; Tue, 16 Oct 2018 10:27:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1539710855; bh=xs1oKAmQZKMnbyQZIWLwz4nucbWh/FytIoNc2quLmoI=; h=From:To:CC:Subject:Date:References:From; b=NrX4xRKiadL8SrUXMTE9PrVRQbomEVrMuQevhBFJBfJfEdOpf0bgsImllmVUWTP0c ohBDPUyXHM+2mBc4w2DbbVq1cDjtin5yc27i1HjnLspt6RHQyS0u1K31MgzIx0nsnE ettaqvgSG2vKXh6mzq6upGfTfBGoqWh2ShTXadRVE2NcmC1/qPQnI6yDVq76+E6khD al6vvU1z3gLDJ5OMpamaymKpn2BQ1aSJaSo5mB5dvER9ZjmE0dQ4LnAbKOnl8m+Y+K 2MbjvoSfWQOvawaWHlraqhYy3GTjANVY7QHr/XdpEQAhtiimSLB88PnBqwAjJNy7ZN p5ZRKAQ9qQfUw== Received: from US01WEHTC2.internal.synopsys.com (us01wehtc2-vip.internal.synopsys.com [10.12.239.238]) by mailhost.synopsys.com (Postfix) with ESMTP id E2AAF308C; Tue, 16 Oct 2018 10:27:34 -0700 (PDT) Received: from US01WEMBX2.internal.synopsys.com ([fe80::e4b6:5520:9c0d:250b]) by US01WEHTC2.internal.synopsys.com ([10.12.239.237]) with mapi id 14.03.0415.000; Tue, 16 Oct 2018 10:27:35 -0700 From: Vineet Gupta To: Eugeniy Paltsev , "linux-snps-arc@lists.infradead.org" CC: "linux-kernel@vger.kernel.org" , "Alexey Brodkin" Subject: Re: [PATCH] ARC: IOC: panic if kernel was started with previously enabled IOC Thread-Topic: [PATCH] ARC: IOC: panic if kernel was started with previously enabled IOC Thread-Index: AQHUW+Pi2l0qN/ga1kOYlHrTlH6D2Q== Date: Tue, 16 Oct 2018 17:27:34 +0000 Message-ID: References: <20181004131212.16405-1-Eugeniy.Paltsev@synopsys.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.144.199.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/04/2018 06:12 AM, Eugeniy Paltsev wrote:=0A= > Disabling and reconfiguring of IOC are quite a tricky actions because=0A= > nobody knows what happens if there're IOC-ahndled tarnsactions in flight= =0A= > when we're disabling IOC.=0A= >=0A= > And the problem is external DMA masters [that were initialized and set=0A= > in a bootlaoder that was executed before we got here] might continue=0A= > to send data to memory even at this point and we have no way to prevent= =0A= > that.=0A= >=0A= > That said it's much safer to not enable IOC at all anywhere before Linux= =0A= > kernel.=0A= >=0A= > As we can build u-boot with IOC support (mostly for debugging purposes)= =0A= > let's check that kernel was started with disabled IOC regardless of=0A= > our plans to use it or not.=0A= >=0A= > Also while I'm at it, replace hardcoded bits in ARC_REG_IO_COH_PARTIAL=0A= > and ARC_REG_IO_COH_ENABLE registers by definitions.=0A= >=0A= > Inspired by: https://lkml.org/lkml/2018/1/19/557=0A= >=0A= =0A= Applied with updated changelog !=0A= =0A= -Vineet=0A=