Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Best Of
Re: Page size for x64
So, do I always need to use a page size of 4K for the FPGA on x64 systems?
So.... that works. So... why not just use that?
Since you're a "hardware guy" and to avoid any confusion: Whenever you read "Logical Address" in the WDK docs, substitute "Physical Address" in your mind. The use of the term "Logical Address" in the WDK is short for "Device Bus Logical Address" and not the same thing that the Intel processor docs refer to as "Logical Address." Technically speaking, from a Windows architecture perspective, "Device Bus Logical Address" is not really the same as a physical address... but for the purposes of our discussion we can say they're the same.
The Page Size -- which is the granularity at which blocks of physical memory are allocated and on which virtual addresses are translated is defined by Windows, and is not changeable. This page size is 4K (modulo large pages, which don't concern you).
I have no idea what the page size in your IP block relates to. The Common Buffer that you allocate in host memory (that IS what we're talking about, right?) will effectively be PHYSICALLY contiguous... but will by default being aligned on a 4K physical address boundary that is conveniDoesent to Windows.
Does that help any?
Peter
Re: ETW Consumer in kernel-mode
Why? I'm not trying to be snarky (well, maybe I am). I just cannot imagine a case where this would be useful. ETW events are intended for human consumption, or for automated analysis tools producing reports for human consumption. The details, the string handling, the I/O -- all of that is just more difficult in the kernel.
Tim's first general rule of Windows programming: Never do anything in the kernel that can be done just as well in user mode.
Re: Not alertable KeWaitForSingleObject()?
Are you simply not reading any of of the carefully worded responses you've received? Or do you think we don't know what we're talking about?
I will state this as a rule. Always specify alertable as FALSE. Always. When you need to violate this rule, you will know it, but it is extremely unlikely that situation will arise. I've been writing Windows drivers for 29 years. I've never needed alertable set to TRUE, and you don't either.
Re: Not alertable KeWaitForSingleObject()?
You do not understand the purpose of "Alertable" it is not related to the object(s) you are waiting on, it is related to things like user space APC's which most drivers do not worry about. So waiting for an object with "Alertable" set FALSE will still wake up when the object is ready.
Don_Burn
Re: Page size for x64
There is a long, sometime torturous, thread on the topic of common buffer alignment here. I strongly recommend you get a cup of coffee and read through the entire thing. Mr. Roberts does some excellent investigation.
Among the findings:
1) It appears you have to use a scatter/gather profile for your alignment to be respected.
2) Use WdfCommonBufferCreateWithConfig instead of relying on the device alignment to be respected.
I’ll be waiting to hear the result of your experiments!
Peter
Community Rules and Guidelines -- Please Read Before Posting
Welcome to the OSR Developer Community
Last Updated: 04 December 2019
These Rules and Guidelines are established for the overall good of the Community. We reserve the right to edit or change them at any time and without notice. For that reason, we recommend you stop by here frequently to check on the latest changes.
This Community and its forums is maintained by OSR Open Systems Resources, Inc. as a public service for the overall benefit of the professional Windows system software development community. The purpose of the Community is to provide help folks who design and develop Windows drivers, file systems, and file system Minifilters with problems, issues, and policies. It's also intended as a place to have focused discussions regarding Windows OS architecture, driver development, file system and Minifilter development, and debugging issues.
The Community is specifically NOT for extended debates and discussions, and we tend not to appreciate answers that start with "In Linux, we do it this way" or "On Android, this would be easy."
We will be creating an FAQ for each of the lists. If you'd like to contribute a question or an answer, please feel free to post about it in the relevant category.
BEHAVIOR
We are a respectful, inclusive, community. We, as a community, will not tolerate behavior that disrespects, harasses, abuses, shames, denigrates, mocks, or otherwise marginalizes any of our members. We will not accept trolling, insulting or derogatory comments, or personal or political attacks.
Incidents of inappropriate conduct on the list will result in that member, and perhaps all members from the offender's company, being permanently banned from the community.
The following are specifically inappropriate behaviors on these forums:
1. Commercial postings - This is a technical community, and the only posts that are allowed are technical in nature. Please don't post advertisements or announcements for your products, services, or activities to the forums. Your posting will NOT be considered technical (and thus legitimate), just because it starts with "I just wanted all you to know that we've released a new version of" some software. On the other hand, if somebody posts question saying "Can anybody recommend a good XYZ?", it's perfectly fine to answer "Yeah, we make XYZ's and we think they're pretty cool. Please contact me directly for more info."
2. Job solicitations - Not from commercial concerns looking for developers, not from head hunters, not from small companies, not from people looking for work, not from consultants looking for clients.
3. Salary, consulting rate or price discussions - Something about the laws here in the States about price fixing comes into play here. Please just don't do it.
4. Use of the email addresses or names of Community members for "direct mail advertising" of any type.
5. Anything that, in the judgment of the moderators, is not in keeping with the overall spirit and purpose of the Community or is not in the best interest of the Windows system software development community as a whole.
There are a number of other behaviors that are considered rules of "good conduct" for posting here on the forums. These include:
1. Please do not revive "old" threads. Please not reply to threads where the last post is more than a month old. This is referred to as "necroposting." If you have a comment/question/issue that's raised in a "dead" thread, just start a new thread (you can post a link to the old thread if you want) and ask your question there.
2. Please post your question in the appropriate category: For example, file system filter questions should be posted to NTFSD; Other Windows driver questions should be posted to NTDEV.
3. Please do not post the same question in multiple categories. This is not allowed.
4. Please do the Community members the courtesy of searching the Internet and the list archives before you post a question.
5. Please post your questions/comments in English. We get that the majority of forum members are not necessarily native speakers of the English language. On the other hand, it is clear to us that the language most forum members share in common is English. If you struggle with English, try not to be too concerned -- The members will typically ask questions if your post is not sufficiently clear.
Students, Hobbyists, Dilettantes, and Dabblers
While we are first and foremost a community of working, professional, system software developers we absolutely welcome (and encourage, even!) questions from students, hobbyists, and those who wish to dabble in the field of Windows drivers. If you're a student, or if you're asking a question out of general curiosity or academic interest, we ask you to please say so in your post. Also, please don't ask us to do your homework for you. We mean that in both the literal sense (you shouldn't bring assignments from your professors here for us to solve for you) and also the more figurative sense (please do some independent research on your problem before asking us here).
Searching
The forums are all searchable from the web site, and can be searched by Google, using the "site:community.osr.com" qualifier. The community will be happiest if you search first, and ask questions after doing so.
Terms of Service and Privacy Policy
Before you use this site, please be sure you read both our Terms of Service and Privacy Policy. Your use of the Community is expressly conditioned on your acceptance of the Terms and Service and Privacy Policy.
Questions About Policies? Ideas? Contacting OSR and the Admins/Mods
You can post here in the Announcements and Administration section if you have questions about the Community. We'll be happy to hear from you. We think.
Yes... Windows 1909 AKA 19H2 Has Been Released
In case you're not yet aware, Windows 1909 (AKA 19H2 AKA 18363.476 AKA... whatever) has been released.
More importantly for our community there is no new or updated WDK, SDK, ADK, or HLK associated with this release.
So now you know.
Peter
Re: Device not started 0x16 (CM_PROB_DISABLE)// Load fail (code39): Object Name not found.
Mybe this is what I am missing. What a License code need to run in kernel? and How can I know if my licensing code not designed to run in kernel?
Whoever provided the code should have told you. Remember that a kernel driver does not have access to ANY user-mode APIs. If they're doing any file I/O, or any Winsock socket calls, or any GDI drawing, or any window messages, or even calls like Sleep, then it isn't kernel code and would need to be rewritten.
CM_PROB_DISABLED usually means that you, the user, disabled the device using Device Manager.