From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC] mac80211_hwsim: report survey data for scanned channels
Date: Sat, 4 Mar 2017 11:10:36 +0200 [thread overview]
Message-ID: <20170304091036.GA5388@w1.fi> (raw)
In-Reply-To: <20170221103118.18441-1-johannes@sipsolutions.net>
On Tue, Feb 21, 2017 at 11:31:18AM +0100, Johannes Berg wrote:
> Currently, hwsim is reporting survey data (only a fake noise floor)
> for the current channel. This breaks when the multi-channel support
> is enabled since then there's no current channel.
>
> Make the dummy implementation closer to a real one and only report
> data while scanning, for all the scanned channels. At other times,
> no survey data might be available (in real hardware) due to power-
> save for example.
> Had this lying around - is it useful for anyone?
Yes, it seems to make the ap_acs hwsim test cases in hostap.git quite a
bit more useful in hitting proper acs.c coverage in hostapd.. And also
allow having to have hacks to force previous AP instance on the same
band just to be able to hit any of this code.
> - survey->filled = SURVEY_INFO_NOISE_DBM;
> + survey->filled = SURVEY_INFO_NOISE_DBM |
> + SURVEY_INFO_CHANNEL_TIME |
> + SURVEY_INFO_CHANNEL_TIME_BUSY;
This is pretty old, though.. :) Had to remove the "CHANNEL_" part
here..
> + survey->channel_time =
> + survey->channel_time_busy = survey->channel_time/8;
.. and "channel_" in these to make this compile. Anyway, with those
trivial changes, the hwsim test cases did start looking more
interesting, so it would seem reasonable to get this applied.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2017-03-04 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 10:31 [RFC] mac80211_hwsim: report survey data for scanned channels Johannes Berg
2017-03-04 9:10 ` Jouni Malinen [this message]
2017-03-06 12:32 ` Johannes Berg
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=20170304091036.GA5388@w1.fi \
--to=j@w1.fi \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).