Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1591305 > unrolled thread

Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME

Started byPaolo Bonzini <pbonzini@redhat.com>
First post2017-03-02 18:20 +0100
Last post2017-03-02 18:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce  buffers with SME Paolo Bonzini <pbonzini@redhat.com> - 2017-03-02 18:20 +0100

#1591305 — Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME

FromPaolo Bonzini <pbonzini@redhat.com>
Date2017-03-02 18:20 +0100
SubjectRe: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME
Message-ID<tgCyu-5uu-23@gated-at.bofh.it>

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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web