From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752592AbdCBRLQ (ORCPT ); Thu, 2 Mar 2017 12:11:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45618 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753930AbdCBRLL (ORCPT ); Thu, 2 Mar 2017 12:11:11 -0500 Subject: Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME To: Tom Lendacky , Konrad Rzeszutek Wilk References: <20170216154158.19244.66630.stgit@tlendack-t1.amdoffice.net> <20170216154619.19244.76653.stgit@tlendack-t1.amdoffice.net> <20170217155955.GK30272@char.us.ORACLE.com> <17c8099a-5495-5f1d-4c8a-bd9f5d2c5e58@amd.com> Cc: linux-arch@vger.kernel.org, linux-efi@vger.kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux-foundation.org, Rik van Riel , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Toshimitsu Kani , Arnd Bergmann , Jonathan Corbet , Matt Fleming , "Michael S. Tsirkin" , Joerg Roedel , Brijesh Singh , Ingo Molnar , Alexander Potapenko , Andy Lutomirski , "H. Peter Anvin" , Borislav Petkov , Andrey Ryabinin , Thomas Gleixner , Larry Woodman , Dmitry Vyukov From: Paolo Bonzini Message-ID: Date: Thu, 2 Mar 2017 18:01:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <17c8099a-5495-5f1d-4c8a-bd9f5d2c5e58@amd.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Thu, 02 Mar 2017 17:01:35 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/02/2017 17:51, Tom Lendacky wrote: > > It's meant just to notify the user about the condition. The user could > then decide to use an alternative device that supports a greater DMA > range (I can probably change it to a dev_warn_once() so that a device > is identified). I would be nice if I could issue this message once per > device that experienced this. I didn't see anything that would do > that, though. dev_warn_once would print once only, not once per device. But if you leave the dev_warn elsewhere, this can be just pr_warn_once. Paolo