site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=4e5U9RhgYEWSrWwcVshnunJIl8h/6aurhw22ZkHbK88=; b=T4lHDzjlrLlviCEKgCImO1IyqrO0hpjSNmF1Vq6byVlbbWSpN+QlDC0cKZZZSR+wrHX5vCbqbzdRU8VTjkGz7BG48yQqz0HqEH8ZCRFZsd68bKynXtLOoCsJlS25eLDJ4oudWHfvshZ1s8o6+YDalxSwxD6ooDTByAQ6Lls2M2U= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TPBfp0JKmmIrl1EoUMS+B3uTuq4IDNKspxghTCuFi29nou/xnzICaXGMO9+ZZwMp3L/LoVLOmFb7XQOmnt6S3e2O5LHx3+4QKT26LzU+cCFpZ7NMLj2tG5QeVUPry+3b29dO4IogFKZJxPuEqZqOiiCjLTGgpCWWRfGfWR8nbco= Quinn, Thanks for the explanation.
Of course, this doesn't help folks who are trying to access CPU physical addresses (-:
I am trying to read a page of physical memory and do an operation on its contents (hash) and then return it to the user.
I suspect you can work around this with the kIOMemoryTypePhysical64 flag, but I haven't looked at it in depth.
From reading the documentation about the IOMemoryDescriptor on developer.apple.com, it seems that calling "withPhysicalAddress" should set the kMemoryTypePhysical flag. Also, I tried allocating memory with IOMalloc instead of throwing it on the kernel stack, which resulted in the same panic. Any other ideas? I guess I'll try setting the flags manually and see how that goes.
Thank you, Timur _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com