From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Marc Marí" <marc.mari.barcelo@gmail.com>,
"Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, "Kevin O'Connor" <kevin@koconnor.net>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc Marí" <markmb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4] Add optionrom compatible with fw_cfg DMA version
Date: Wed, 03 Feb 2016 09:44:35 +0100 [thread overview]
Message-ID: <1454489075.4967.45.camel@redhat.com> (raw)
In-Reply-To: <56B0C59A.6070008@redhat.com>
Hi,
> I think the "dma_enabled" property is not exposed to the user.
It is: "-global fw_cfg.dma_enabled=off" works (as in: doesn't throw an
error). Has no effect through as it gets overridden later on.
> The default value of "dma_enabled" in both fw_cfg_io_properties and
> fw_cfg_mem_properties is irrelevant; the actual property value is always
> overwritten in fw_cfg_init_io_dma() and fw_cfg_init_mem_wide(), which
> all of the init paths go through.
And IMHO we should not do that, so setting the property actually has an
effect.
> I agree that DMA capability should be filtered with machine type.
> However, that distinction should not be made using the current
> "dma_enabled" properties (i.e., of "fw_cfg_io_properties" and
> "fw_cfg_mem_properties". Instead, it should be made in the
> board-specific callers of fw_cfg_init_(io_dma|mem_wide).
Why?
cheers,
Gerd
next prev parent reply other threads:[~2016-02-03 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 11:12 [Qemu-devel] [PATCH v4] Add optionrom compatible with fw_cfg DMA version Marc Marí
2016-01-29 15:25 ` Stefan Hajnoczi
2016-02-02 11:06 ` Gerd Hoffmann
2016-02-02 12:04 ` Gerd Hoffmann
2016-02-02 13:07 ` Marc Marí
2016-02-02 14:23 ` Gerd Hoffmann
2016-02-02 15:04 ` Laszlo Ersek
2016-02-03 8:44 ` Gerd Hoffmann [this message]
2016-02-03 11:48 ` Laszlo Ersek
2016-02-03 12:57 ` Gerd Hoffmann
2016-02-02 12:58 ` Marc Marí
2016-02-03 9:47 ` Stefan Hajnoczi
2016-02-22 11:56 ` Vladimir Sementsov-Ogievskiy
2016-02-23 9:51 ` Stefan Hajnoczi
2016-03-21 11:14 ` Richard W.M. Jones
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=1454489075.4967.45.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=kevin@koconnor.net \
--cc=lersek@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=markmb@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).